Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core
Hi forks, Thanks for inviting me to Core team! I'll do my best and I hope to contribute for Horizon than before. Best regards, --- Kenji Ishii > -Original Message- > From: Richard Jones [mailto:r1chardj0...@gmail.com] > Sent: Monday, November 21, 2016 1:31 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core > > As a result of the unanimous vote here, I welcome Kenji to the Horizon > Core Team! > > > Richard > > On 19 November 2016 at 12:37, Tripp, Travis S > wrote: > > +1 > > > > > > > > From: Timur Sufiev > > Reply-To: OpenStack List > > Date: Friday, November 18, 2016 at 1:34 AM > > To: OpenStack List > > > > > > Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core > > > > > > > > +1 > > > > > > > > On Fri, Nov 18, 2016 at 12:35 AM Thai Q Tran wrote: > > > > +1 from me. Kenji is also very active in the plugin space. > > > > > > > > - Original message - > > From: David Lyle > > To: "OpenStack Development Mailing List (not for usage questions)" > > > > Cc: > > Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core > > Date: Thu, Nov 17, 2016 11:51 AM > > > > > > +1 > > > > On Tue, Nov 15, 2016 at 5:02 AM, Akira Yoshiyama > > wrote: > >> +1 > >> > >> 2016年11月15日(火) 20:47 Rob Cresswell (rcresswe) > : > >>> > >>> Big +1 from me > >>> > >>> > On 14 Nov 2016, at 00:24, Richard Jones > wrote: > >>> > > >>> > Hi Horizon core team, > >>> > > >>> > I propose Kenji Ishii as a new Horizon core reviewer. Kenji has > >>> > been a solid Horizon contributor for some time, with thoughtful > >>> > and helpful reviews showing good judgment and good knowledge of > >>> > Horizion and related systems. Please respond with your votes by > Friday. > >>> > > >>> > > >>> > Thanks, > >>> > > >>> >Richard > >>> > > >>> > > >>> > > >>> > > __ > >>> > OpenStack Development Mailing List (not for usage > >>> > questions) > >>> > Unsubscribe: > >>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >>> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >>> > >>> > >>> > >>> > > >>> __ OpenStack Development Mailing List (not for usage questions) > >>> Unsubscribe: > >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > >> > >> > _ > >> _ OpenStack Development Mailing List (not for usage questions) > >> Unsubscribe: > >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >> > > > > > _ > _ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > > > > > _ > _ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > > > _ > _ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _ > _ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Horizon] Zhenguo Niu retiring from Horizon Core Team
Hi folks, Zhenguo Niu has been a core for many cycles, for which I thank him. His focus and time has shifted away from UI though, so he's asked to be removed from the core team. Thanks again, Zhenguo! Richard __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core
As a result of the unanimous vote here, I welcome Kenji to the Horizon Core Team! Richard On 19 November 2016 at 12:37, Tripp, Travis S wrote: > +1 > > > > From: Timur Sufiev > Reply-To: OpenStack List > Date: Friday, November 18, 2016 at 1:34 AM > To: OpenStack List > > > Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core > > > > +1 > > > > On Fri, Nov 18, 2016 at 12:35 AM Thai Q Tran wrote: > > +1 from me. Kenji is also very active in the plugin space. > > > > - Original message - > From: David Lyle > To: "OpenStack Development Mailing List (not for usage questions)" > > Cc: > Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core > Date: Thu, Nov 17, 2016 11:51 AM > > > +1 > > On Tue, Nov 15, 2016 at 5:02 AM, Akira Yoshiyama > wrote: >> +1 >> >> 2016年11月15日(火) 20:47 Rob Cresswell (rcresswe) : >>> >>> Big +1 from me >>> >>> > On 14 Nov 2016, at 00:24, Richard Jones wrote: >>> > >>> > Hi Horizon core team, >>> > >>> > I propose Kenji Ishii as a new Horizon core reviewer. Kenji has been a >>> > solid Horizon contributor for some time, with thoughtful and helpful >>> > reviews showing good judgment and good knowledge of Horizion and >>> > related systems. Please respond with your votes by Friday. >>> > >>> > >>> > Thanks, >>> > >>> >Richard >>> > >>> > >>> > >>> > __ >>> > OpenStack Development Mailing List (not for usage questions) >>> > Unsubscribe: >>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> >>> __ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [docs][upgrades] time to add official docs for upgrading services?
How about top-level organization by project/service, each with consistent topics that pertain to installation, configuration, upgrades, development, API, etc? Projects can determine whether some or all of those topics reside in the openstack-manuals or project repository. On Fri, Nov 18, 2016 at 12:27 PM, Doug Hellmann wrote: > Excerpts from Steve Martinelli's message of 2016-11-17 20:36:46 -0500: > > In the keystone docs we have notes about how to upgrade between releases > > [1], so does the nova team [2]. > > > > Is it time we create an official guides to [3] for this subject? > > > > [1] http://docs.openstack.org/developer/keystone/upgrading.html > > [2] http://docs.openstack.org/developer/nova/upgrade.html > > [3] http://docs.openstack.org/ > > Maybe, instead of creating a separate project-specific guide for > every topic (install, upgrade, config, API, etc.), it would make > sense to have developer, deployer, and user facing guides and create > separate chapters in each for topics relevant to the audiences? > > Doug > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tricircle]meetup in OpenStack-Bug-Smash-Ocata-Shenzhen
Hello, There is bug smash as usual in China for Ocata, which will be held from Nov. 30 - Dec. 2, 2016 at Shenzhen China. https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Ocata-Shenzhen How about to have a meetup together with the bug-smash: we gather and sit together, and I also discussed with the organizer to arrange us sit together with Neutron or close to Neutron table. Let's meet and talk any topic you are interested in. For Tricircle has just been accepted as one of big-tent project, and during the Barcelona summit, some guys from Intel hope that Tricircle can give one short introduction about the design update during the bug smash, I'll talk to bug-smash organizer to see how to arrange this. Please join us in the bug-smash if you are interested in Tricircle, the link is here: https://etherpad.openstack.org/p/OpenStack-Bug-Smash-Ocata-Shenzhen. Best Regards Chaoyi Huang (joehuang) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo][ci] jobs shuffle to add IPv6 coverage
On Tue, Nov 15, 2016 at 11:41 AM, Gabriele Cerami wrote: > On 18 Oct, Gabriele Cerami wrote: >> Hello, >> >> after adding coverage in CI for HA IPv6 scenario here >> https://review.openstack.org/363674 we wanted to add IPv6 testing on the >> gates. >> To not use any more resources the first suggestion to add IPv6 to the >> gates was to make all HA jobs IPv6, move network isolation testing for >> IPv4 on non-ha job, and test non-netiso environment on multinode. > > This is still up for debate, another possibility is to test IPv6 just in > the updates jobs. > >> This is almost done here https://review.openstack.org/382515 with one >> exception. Liberty HA IPv6 fails during ping test with the error: >> 503 Service unavailable. > > This issue was solved during the summit > >> Moreover, swift memecache code in liberty is clearly not IPv6 >> compatible, it gives an error on the overcloud, not being able to get >> host and port from a correctly formed IPv6 URL. To make it compatible >> with IPv6 this should be backported https://review.openstack.org/258704 > > This still remains. > >> Before continuing the debugging I wanted to be sure that: >> - this is an acceptable shuffle for the gates jobs >> - we are really interested in testing liberty IPv6 > > I have another question to add to the mix. Do we care to test IPv6 with > SSL ? Our current certificate handling code is dealing only with IPv4 > addresses, so if we need to test both, we'll have to add that part too. Definitely yes, I think most of people who go in production with IPv6 has SSL, so it should be the standard imho. -- Emilien Macchi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tripleo] containerized compute CI status
Hey Wes, Thanks for this update, really useful. On Fri, Nov 11, 2016 at 4:20 PM, Wesley Hayutin wrote: > Greetings, > > I wanted to send a status update on the containerized compute CI, this is > still very much a work in progress and is not yet working end to end. I'm > hoping by sending this out early in the process we'll all benefit from > developing the CI as the feature is developed. Awesome! I've been planning to work on $topic after my PTOs and I'm glad we have some help here. The current status of Container CI job is very bad, broken and needs some love. Is there anything you engaged already about using oooq + this new role in our upstream CI? > Everything you'll need to know to use this is documented here [1], I have > two issues that I'm filling out details on [2] > > Any feedback w/ regards to the role, the documentation or in general is > welcome. I hope if you try this, you find it easy to understand and develop > with. In the future, we might want to avoid new modules/roles/whatever things related to TripleO living outside OpenStack governance, so it helps to involve TripleO reviewers more easily and bring more visibility, transparency and consistency in how we work. Let me know what you think. > Thank you! > > > [1] > https://github.com/redhat-openstack/ansible-role-tripleo-overcloud-prep-containers/ > [2] > https://github.com/redhat-openstack/ansible-role-tripleo-overcloud-prep-containers/issues > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Emilien Macchi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Congress] Magnum_driver
Hi everybody,
As suggested by Tim I've checked what JSON data magnum is returning on the CLI
by adding the --debug parameter to the magnum CLI commands.
magnum --debug cluster-template-list
RESP BODY: {"clustertemplates": [{"insecure_registry": null, "links": [{"href":
"http://10.0.2.15:9511/v1/clustertemplates/8d25a1ed-faa6-4305-a6a1-6559708c805b";,
"rel": "self"}, {"href":
"http://10.0.2.15:9511/clustertemplates/8d25a1ed-faa6-4305-a6a1-6559708c805b";,
"rel": "bookmark"}], "http_proxy": null, "updated_at": null,
"floating_ip_enabled": true, "fixed_subnet": null, "master_flavor_id": "my",
"uuid": "8d25a1ed-faa6-4305-a6a1-6559708c805b", "no_proxy": null,
"https_proxy": null, "tls_disabled": false, "keypair_id": "testkey", "public":
false, "labels": {}, "docker_volume_size": 7, "server_type": "vm",
"external_network_id": "public", "cluster_distro": "fedora-atomic", "image_id":
"fedora-atomic-latest", "volume_driver": null, "registry_enabled": false,
"docker_storage_driver": "devicemapper", "apiserver_port": null, "name":
"k8s-cluster-template", "created_at": "2016-11-11T11:38:25+00:00",
"network_driver": "flannel", "fixed_network": null, "coe": "kubernetes",
"flavor_id": "m
1.tiny", "master_lb_enabled": false, "dns_nameserver": "193.205.160.3"}]}
magnum --debug cluster-list
RESP BODY: {"clusters": [{"status": "CREATE_FAILED", "cluster_template_id":
"8d25a1ed-faa6-4305-a6a1-6559708c805b", "uuid":
"1634beb9-25de-4cdd-bafa-67537069f0cc", "links": [{"href":
"http://10.0.2.15:9511/v1/clusters/1634beb9-25de-4cdd-bafa-67537069f0cc";,
"rel": "self"}, {"href":
"http://10.0.2.15:9511/clusters/1634beb9-25de-4cdd-bafa-67537069f0cc";, "rel":
"bookmark"}], "stack_id": "17f1248d-286a-4fd4-9639-af5773670f03", "keypair":
"testkey", "master_count": 1, "node_count": 1, "create_timeout": 60, "name":
"k8s-cluster"}]}
I've modified the magnum_driver and the unit test for it, but I still have some
errors.
Anyway, I've added the magnum_driver code and its unit test to review.
Ruben
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
