Re: [openstack-dev] [os-upstream-institute][all] Get together at the PTG
I'd love to join in team gathering and meeting, too. I'm ok to pick Monday or Tuesday now that most of you choose it. Cheers, Hanxi Liu On Fri, Aug 25, 2017 at 10:36 PM, Ildiko Vancsa wrote: > Hi Training Team and All, > > As we have our next PTG coming up shortly I think that would be a great > opportunity for the team and everyone who’s interested to meet and check > where we are and what our future plans are. :) > > I would like to ask you to raise your hand by replying to this mail if you > will be around during the PTG week in Denver and would be interested in > joining. Please also indicate your availability for the week. > > Based on the responses we will pick a day and a time that works best for > most to have our gathering. > > Please let me know if you have any questions. > > Thanks and Best Regards, > Ildikó > (IRC: ildikov) > > > > __ > 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] [os-upstream-institute][all] Get together at the PTG
Would like to join the meeting if I' am free on Monday or Tuesday, though I wasn't involved too much before. 2017-08-28 9:35 GMT+08:00 Ghanshyam Mann : > I will be there and Monday or Tuesday works better for me too. > > -gmann > > > On Sat, Aug 26, 2017 at 2:41 AM, Kendall Nelson > wrote: > > I'll be around obviously. > > > > Monday or Tuesday would work best for me as well. > > > > -Kendall (diablo_rojo) > > > > On Fri, Aug 25, 2017 at 8:09 AM Miguel Lavalle > wrote: > >> > >> Ildiko, > >> > >> For me it would be great if we can meet on Monday or Tuesday. Those two > I > >> have also to find time to get together with the Docs team > >> > >> Regards > >> > >> On Fri, Aug 25, 2017 at 9:36 AM, Ildiko Vancsa > > >> wrote: > >>> > >>> Hi Training Team and All, > >>> > >>> As we have our next PTG coming up shortly I think that would be a great > >>> opportunity for the team and everyone who’s interested to meet and > check > >>> where we are and what our future plans are. :) > >>> > >>> I would like to ask you to raise your hand by replying to this mail if > >>> you will be around during the PTG week in Denver and would be > interested in > >>> joining. Please also indicate your availability for the week. > >>> > >>> Based on the responses we will pick a day and a time that works best > for > >>> most to have our gathering. > >>> > >>> Please let me know if you have any questions. > >>> > >>> Thanks and Best Regards, > >>> Ildikó > >>> (IRC: ildikov) > >>> > >>> > >>> > >>> > >>> > __ > >>> 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 > -- ChangBo Guo(gcb) __ 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] [Mogan]Tasks update of Mogan Project
Hi, We are glad to present this week's tasks update of Mogan. We have finish a lot of wonderful work in Pike release, and Mogan will have her first release! See the details below: Essential Priorities == 1. Node aggregates (liudong, zhangyang, zhenguo) blueprint: https://blueprints.launchpad.net/mogan/+spec/node-aggregate spec: https://review.openstack.org/#/c/470927/ merged code: Adds aggregates DB model and API https://review.openstack.org/#/c/482786/ merged Add aggregate object https://review.openstack.org/#/c/484630/ merged Add aggregate API https://review.openstack.org/#/c/484690/9 merged Retrieve availability zone from aggregate https://review.openstack.org/#/c/485506/ merged Add node list support https://review.openstack.org/#/c/486016/ merged Add aggregate nodes API https://review.openstack.org/#/c/487284/ merged Add aggregates tests https://review.openstack.org/#/c/488296/ merged Add Checks for aggregate availability_zone https://review.openstack.org/#/c/489876/ merged Add Checks for aggregate affinity_zone https://review.openstack.org/#/c/493495/ 2. Server groups and scheduler hints(liudong, liusheng) blueprint: https://blueprints.launchpad.net/mogan/+spec/server-group-api-extension https://blueprints.launchpad.net/mogan/+spec/support-schedule-hints spec:https://review.openstack.org/#/c/489541/ code: scheduler hints: https://review.openstack.org/#/c/463534/ server groups: https://review.openstack.org/488298 https://review.openstack.org/488909 https://review.openstack.org/489850 https://review.openstack.org/#/c/490328/ schedule hints: Add support for scheduler_hints https://review.openstack.org/#/c/463534/ Use server group in scheduler https://review.openstack.org/#/c/496151/ 3. Adopt servers (wanghao, litao) blueprint: https://blueprints.launchpad.net/mogan/+spec/manage-existing-bms spec: https://review.openstack.org/#/c/459967/ merged code: https://review.openstack.org/#/c/479660/ merged https://review.openstack.org/#/c/481544/ 4. Add socat console support (zhenguo) https://review.openstack.org/#/c/493836/ Move to Queens = 1. Valence integration (zhenguo, shaohe, luyao, Xinran) Move to next cycle. blueprint: https://blueprints.launchpad.net/mogan/+spec/valence-integration spec: https://review.openstack.org/#/c/441790/3/specs/pike/approved/valence-integration.rst No updates 2. Support boot-from-volume in Mogan(wanghao, zhenguo) Move to next cycle blueprint: https://blueprints.launchpad.net/mogan/+spec/support-boot-from-volume-in-mogan code: https://review.openstack.org/#/c/489455/ Optional Priorities == 1. support runnig api server under uwsgi https://review.openstack.org/#/c/482057/ merged 2. Documentation (zhenguo, liusheng) Add states and transitons diagram https://review.openstack.org/471293 Add sample config and policy files to mogan docs https://review.openstack.org/471637 add documentation about testing https://review.openstack.org/#/c/472028 __ 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] [os-upstream-institute][all] Get together at the PTG
I will be there and Monday or Tuesday works better for me too. -gmann On Sat, Aug 26, 2017 at 2:41 AM, Kendall Nelson wrote: > I'll be around obviously. > > Monday or Tuesday would work best for me as well. > > -Kendall (diablo_rojo) > > On Fri, Aug 25, 2017 at 8:09 AM Miguel Lavalle wrote: >> >> Ildiko, >> >> For me it would be great if we can meet on Monday or Tuesday. Those two I >> have also to find time to get together with the Docs team >> >> Regards >> >> On Fri, Aug 25, 2017 at 9:36 AM, Ildiko Vancsa >> wrote: >>> >>> Hi Training Team and All, >>> >>> As we have our next PTG coming up shortly I think that would be a great >>> opportunity for the team and everyone who’s interested to meet and check >>> where we are and what our future plans are. :) >>> >>> I would like to ask you to raise your hand by replying to this mail if >>> you will be around during the PTG week in Denver and would be interested in >>> joining. Please also indicate your availability for the week. >>> >>> Based on the responses we will pick a day and a time that works best for >>> most to have our gathering. >>> >>> Please let me know if you have any questions. >>> >>> Thanks and Best Regards, >>> Ildikó >>> (IRC: ildikov) >>> >>> >>> >>> >>> __ >>> 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] [all][QA][group-based-policy][zaqar][packaging_deb][fuel][networking-*] Marking <= mitaka EOL
Hi Tony, TBH, I have no idea what happened for Zaqar's Liberty. So I don't think we need a liberty2. Thanks. On 24/08/17 15:14, Tony Breeds wrote: > Hello all, > We have a number of old stable/* branches hanging around and I'd > like to mark anything <= stable/mitaka as EOL. I've highlighted a few > projects on the subject line: > > QA: Are the older branches of grenade safe to go? IIUC we don't use > them as we don't do grenade testing on $oldest stable branch > group-based-policy: In the past you've requested your old branches stay > around Do you still need this? Is there value in > the *all* staying active? > zaqar: I see that liberty was EOL and then reactivated do you still need >liberty2? > packaging_deb: As these repos have the $project origin using the >standard series-eol tag doesn't make sense for exaxple >deb-nova gets a mitaka-eol from the nova repo. So I've >picked mitaka-eol-dpkg. > fuel, networking-*: There are several entries for these projects groups > so I'm calling them out here for attention. > > I'm proposing we do this removal during the PTG. Once we've done the > series based branches we can look at old versioned releases like > stable/16.04 etc. > > It's hard to present the data in a clear way so given infra will be the > ultimate actioners of this list I present this as a shell script: > > --- > eol-branch.sh -- stable/essex essex-eol openstack/anvil > eol-branch.sh -- stable/folsom folsom-eol openstack/anvil > eol-branch.sh -- stable/grizzly grizzly-eol openstack/anvil > eol-branch.sh -- stable/havana havana-eol openstack/openstack > eol-branch.sh -- stable/icehouse icehouse-eol \ > openstack/astara openstack/networking-brocade \ > openstack/networking-cisco openstack/networking-mlnx \ > openstack/networking-odl openstack/networking-plumgrid \ > openstack/nova-solver-scheduler \ > openstack/sahara-image-elements openstack/tricircle \ > openstack/trio2o openstack/vmware-nsx > eol-branch.sh -- stable/icehouse icehouse-eol-dpkg \ > openstack/deb-networking-cisco \ > openstack/deb-networking-mlnx openstack/deb-networking-odl > eol-branch.sh -- stable/juno juno-eol \ > openstack/astara openstack/astara-appliance \ > openstack/astara-horizon openstack/astara-neutron \ > openstack/group-based-policy \ > openstack/group-based-policy-automation \ > openstack/group-based-policy-ui openstack/mistral \ > openstack/mistral-dashboard openstack/mistral-extra \ > openstack/networking-bigswitch \ > openstack/networking-brocade openstack/networking-cisco \ > openstack/networking-mlnx openstack/networking-odl \ > openstack/networking-plumgrid \ > openstack/nova-solver-scheduler \ > openstack/openstack-resource-agents \ > openstack/powervc-driver openstack/proliantutils \ > openstack/puppet-n1k-vsm openstack/puppet-vswitch \ > openstack/python-group-based-policy-client \ > openstack/python-mistralclient \ > openstack/python-muranoclient openstack/vmware-nsx > eol-branch.sh -- stable/juno juno-eol-dpkg \ > openstack/deb-mistral openstack/deb-networking-cisco \ > openstack/deb-networking-mlnx openstack/deb-networking-odl \ > openstack/deb-python-mistralclient \ > openstack/deb-python-muranoclient \ > openstack/deb-python-proliantutils > eol-branch.sh -- stable/kilo kilo-eol \ > openstack-dev/grenade openstack/murano-apps \ > openstack/networking-h3c openstack/requirements > eol-branch.sh -- stable/kilo kilo-eol1 \ > openstack/group-based-policy \ > openstack/group-based-policy-automation \ > openstack/group-based-policy-ui \ > openstack/python-group-based-policy-client > eol-branch.sh -- stable/kilo_v2 kilo_v2-eol openstack/networking-bigswitch > eol-branch.sh -- stable/liberty liberty-eol \ > openstack-dev/grenade openstack/ceilometer-powervm \ > openstack/ceilometer-zvm openstack/ceilometermiddleware \ > openstack/fuel-plugin-calico openstack/group-based-policy \ > openstack/group-based-policy-automation \ > openstack/group-based-policy-ui openstack/mistral-extra \ > openstack/networking-infoblox openstack/networking-powervm \ > openstack/networking-zvm openstack/nova-powervm \ > openstack/nova-zvm-virt-driver \ > ope
