Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 2019 14:55
    theopenlab-ci[bot] commented #488
  • Jan 31 2019 14:46
    vadimstroganov starred fog/fog-openstack
  • Jan 31 2019 14:41
    vadimstroganov commented #487
  • Jan 31 2019 14:40
    vadimstroganov commented #487
  • Jan 31 2019 14:38
    vadimstroganov opened #488
  • Jan 31 2019 14:33
  • Jan 31 2019 12:24
    vadimstroganov opened #487
  • Jan 31 2019 09:36
    aufi labeled #486
  • Jan 31 2019 09:35

    aufi on master

    Created explicit mock and real … Merge pull request #486 from gi… (compare)

  • Jan 31 2019 09:35
    aufi closed #486
  • Jan 30 2019 16:38
    gildub closed #482
  • Jan 30 2019 16:38

    gildub on master

    Add multiattach parameter to vo… Merge pull request #482 from ma… (compare)

  • Jan 30 2019 16:38
    gildub commented #482
  • Jan 30 2019 16:23
    theopenlab-ci[bot] commented #486
  • Jan 30 2019 16:07
    gildub synchronize #486
  • Jan 30 2019 15:54
    gildub review_requested #486
  • Jan 30 2019 15:53
    gildub opened #486
  • Jan 30 2019 15:22

    gildub on master

    Fixed a couple of path to clear… Merge pull request #485 from gi… (compare)

  • Jan 30 2019 15:22
    gildub closed #485
  • Jan 30 2019 12:06
Marco Voelz
@voelzmo
Hello friends of the ruby-managed openstack
Can we get fog/fog-openstack#340 merged and a release including that? We're currently packaging our fork of the gem just because of this and I'd like to change that :)
Marco Voelz
@voelzmo
Hey @gildub any chance to get a release including fog/fog-openstack#340? Also, not sure how to proceed with fog/fog-openstack#345 I've just opened it for not losing context
Leo Marlin
@liaodalin19903
who can help me with this, friends?
Leo Marlin
@liaodalin19903
who know this issue?
oblutak
@oblutak
Anyone aware of fog-core 2.0.0 change that breaks fog-openstack?
I never work with fog directly. Encounter the issue using test-kitchen, which is using kitchen-openstack. I have force via my gem file to have fog-core <2.0.0 and I don't see the issue. otherwise test-kitchen fails with
D      ----End Backtrace-----
D      -Composite Exception--
D      Class: Kitchen::ActionFailed
D      Message: Failed to complete #create action: [undefined method `each_pair' for "  <Fog::Compute::OpenStack::Metadata\n    [\n          \n    ]\n  >":Fog::Compute::OpenStack::Metadata
Did you mean?  each_slice]
oblutak
@oblutak
I see the travis build with similar error, so I guess someone will have a look and fix
zz9pzza
@zz9pzza
+1 on the fog-core 2.0.0 change
Ladislav Smola
@Ladas
fog-openstack 0.1.23 released
Gilles Dubreuil
@gildub
@/all. Openlab needs a Ruyb SDK for Openstack, fog-openstack and misty are the two contenders. The thing is that fog-openstack has a long history and user base but lacks updates and the dynamic misty offers with a younger approach. I believe we could have fog-openstack based on misty, which can server as Openstack API conduit (as lower layer). Anyone interested? Thoughts please.
Ladislav Smola
@Ladas
@gildub if we can generate the code we are writing manually, lets go for it :-)
Gilles Dubreuil
@gildub
@Ladas, yeah exactly! :)
Marco Voelz
@voelzmo
Hey, can someone please take a look at fog/fog-openstack#356
version 0.1.23 is broken for a few customers, the issue links to one of our PRs fixing it, a merge and release would be great
Gilles Dubreuil
@gildub
@Ladas, I've burned few cycles to investigate how to use Misty as a 'plugin' but the fog-core coupling is quite deep within. I thought it was a good idea but I'm gonna need more time...
Marek Aufart
@aufi
Hi, are steps how to re-record VCR tests available somewhere?
edigleisonb
@edigleisonb
When I installed the Mitaka version of openstack with devstack. I made the following settings: @connection_params = {
irb(main):019:1 openstack_auth_url: "http://MyIP:5000/v3/auth/tokens",
irb(main):020:1
openstack_username: "admin",
irb(main):021:1 openstack_api_key: "devstack",
irb(main):022:1
openstack_project_name: "admin",
irb(main):023:1* openstack_domain_id: "default"
irb(main):024:1> } I make the: compute = Fog::Compute::OpenStack.new(@connection_params) -> and returns me the following error ---------------- Fog::OpenStack::Errors::ServiceUnavailable: OpenStack compute binding only supports version v2 and v2.1 ------------------- can anybody help me? please
edigleisonb
@edigleisonb
@voelzmo @gildub
Marek Aufart
@aufi
Would it be possible get a new release (I'm interested in fog/fog-openstack#379 to be part of a release)
Marco Voelz
@voelzmo
Hey, it seems a new version of fog-openstack was released (0.1.25). There's no tag on the repository, though, so it is hard to tell what was released. Not sure what the current release process looks like, but could someone please add the corresponding tag? As there are no release notes, that's pretty much my only chance of finding out what I'm getting when updating.
Marco Voelz
@voelzmo
@Ladas @gildub ^^
Ladislav Smola
@Ladas
@gildub did you do a release without tagging it?
jaygeet
@jaygeet
what is fog?
what is openstack?
how both are related?
Sean Handley
@seanhandley
@jaygeet OpenStack is an open source cloud toolkit. If you're familiar with AWS cloud services, then using OpenStack you could build your own cloud with compute/storage/network functions etc. Fog is a Ruby library for interacting with cloud services, one of which is OpenStack, but it support many others.
Gilles Dubreuil
@gildub
@Ladas, did I?
jaygeet
@jaygeet
@seanhandley how openstack is related to nextcloud/owncloud?
or no relation?
openstack is used with virtualbox or qemy kind of stuffs?
which are other competitors/equivalent solution like openstack?
whcih are other fog channels ?
found fog-client and fog-aws
why not fog-server?
Sean Handley
@seanhandley
I don't know anything about owncloud/nextcloud @jaygeet
in terms of competition - I don't know of any open source toolkits for building cloud infrastructure services that's on a par with OpenStack, although Kubernetes does the same job in the container ecosystem. I'd describe them as complimentary tools rather than competitors.
there's no fog-server because fog is a client tool - it wraps up the necessary API calls needed to work with cloud services. So the cloud service providers run the servers - and Fog consumes those services via the APIs they expose.
Gilles Dubreuil
@gildub
@jaygeet, OpenStack is an IaaS, Nextcloud provides file hosting services, not in the same universe at all.
ravenpi
@ravenpi
Dumb Question (maybe): I'm trying to use Fog against a Juno cloud, which presents as running Nova API 1.1, thus throwing an "OpenStack compute binding only supports version v2 and v2.1" error. However, the v2 API does seem to exist -- it's just not listed as an endpoint. Is there a way to override the API endpoints that Keystone returns?
Marek Aufart
@aufi
Hi, you can create a new endpoint or update existing via OpenStack CLI, in new versions there should be powerful openstack command. I think that in Juno, there should be keystone command for this purpose.
$ openstack endpoint create ... or something like $ keystone endpoint-create ...
ravenpi
@ravenpi
sigh . Yeah, fair enough. Your answer is almost certainly the right one. What's got me puzzled, though, is that there are guys here using Fog -- against the same cloud I'm trying to -- for whom it's clearly working. I thought perhaps there was a Fog-side mechanism to deal with "hidden" API endpoints. Maybe they modified the code or something; I'll poke around.
ravenpi
@ravenpi
Huh. I downgraded to charm rev 0.1.22 -- the same one the dev team uses -- and lo! It all works. Regression of some sort?
Gilles Dubreuil
@gildub
Please @/all anyone to review fog/fog-openstack#396 ? And also fog/fog-openstack#397 and fog/fog-openstack#398.
Gilles Dubreuil
@gildub
@/all fog/fog-openstack#413 re-factors bootstrapping to connect a service by covering authentication (token, catalog) and endpoints consumption. This allows to get closer to the OpenStack API guidances and also offers more flexibility with endpoints whether they are 'version less' or not.
Gilles Dubreuil
@gildub
@geemus, @mdarby, @dhague, @seanhandley , core/founders/etc are welcome to help review ^
If not you then nobody can! ;)
Jonas Wielicki
@horazont

Heyo. I am probably stupid, but to me fog-openstack 0.2.0 is broken beyond usability.
This is what I do:

require 'fog/openstack'

conn = Fog::Identity::OpenStack.new(
  openstack_auth_url: 'https://identity.service.example',
  openstack_username: 'my-username',
  openstack_api_key: 'my-password',
  openstack_project_name: 'my-project',
  openstack_domain_id: 'default'
)

print(conn.domains)

I get the following error:

excon.error.response
  :body          => "{\"error\": {\"message\": \"(https://identity.service.example:35357/v3/v3/domains): The resource could not be found.\", \"code\": 404, \"title\": \"Not Found\"}}"
  :cookies       => [
  ]
  :headers       => {
    "Content-Length"         => "154"
    "Content-Type"           => "application/json"
    "Date"                   => "Wed, 29 Aug 2018 11:59:40 GMT"
    "Server"                 => "Apache/2.4.18 (Ubuntu)"
    "Vary"                   => "X-Auth-Token"
    "x-openstack-request-id" => "req-c158339b-10bb-480b-b470-c664f6ea62e4"
  }
  :host          => "identity.service.example"
  :local_address => "192.168.100.177"
  :local_port    => 50442
  :path          => "/v3/v3/domains"
  :port          => 35357
  :reason_phrase => "Not Found"
  :remote_ip     => "185.x.y.z"
  :status        => 404
  :status_line   => "HTTP/1.1 404 Not Found\r\n"
        from /home/jssfr/.chefdk/gem/ruby/2.3.0/gems/excon-0.62.0/lib/excon/middlewares/response_parser.rb:9:in `response_call'
        from /home/jssfr/.chefdk/gem/ruby/2.3.0/gems/excon-0.62.0/lib/excon/connection.rb:414:in `response'
        from /home/jssfr/.chefdk/gem/ruby/2.3.0/gems/excon-0.62.0/lib/excon/connection.rb:263:in `request'
        from /home/jssfr/.chefdk/gem/ruby/2.3.0/gems/fog-core-1.45.0/lib/fog/core/connection.rb:81:in `request'
        from /home/jssfr/.chefdk/gem/ruby/2.3.0/gems/fog-openstack-0.2.0/lib/fog/openstack/core.rb:53:in `request'
        from /home/jssfr/.chefdk/gem/ruby/2.3.0/gems/fog-openstack-0.2.0/lib/fog/identity/openstack/v3/requests/list_domains.rb:7:in `list_domains'
        from /home/jssfr/.chefdk/gem/ruby/2.3.0/gems/fog-openstack-0.2.0/lib/fog/identity/openstack/v3/models/domains.rb:18:in `all'
        from /home/jssfr/.chefdk/gem/ruby/2.3.0/gems/fog-core-1.45.0/lib/fog/core/collection.rb:112:in `lazy_load'
        from /home/jssfr/.chefdk/gem/ruby/2.3.0/gems/fog-core-1.45.0/lib/fog/core/collection.rb:16:in `to_s'
        from test.rb:11:in `write'
        from test.rb:11:in `print'
        from test.rb:11:in `<main>'

The same thing works in fog-openstack 0.1.27 if I add v3/auth/tokens to the URL.