sent from the road
> On Aug 9, 2016, at 5:00 AM, [email protected] > wrote: > > Send OpenStack-operators mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OpenStack-operators digest..." > > > Today's Topics: > > 1. Re: migration leaves instance in VERIFY_RESIZE and does not > clean up source host resources (Gustavo Randich) > 2. Re: [nova] can we lock RPC version with upgrade_levels on > neutron-openvswitch-agent ? (Ihar Hrachyshka) > 3. Re: [nova] can we lock RPC version with upgrade_levels on > neutron-openvswitch-agent ? (Micha? Jastrz?bski) > 4. Ops Meetups Team - Next Meeting Coordinates and News (Tom Fifield) > 5. Re: Ops Meetups Team - Next Meeting Coordinates and News > (Tom Fifield) > 6. Re: Ops Meetups Team - Next Meeting Coordinates and News > (Melvin Hillsman) > 7. Re: VirtIO and IDE disk (Emilio Moreno Fernandez) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 8 Aug 2016 18:31:21 -0300 > From: Gustavo Randich <[email protected]> > To: "[email protected]" > <[email protected]> > Subject: Re: [Openstack-operators] migration leaves instance in > VERIFY_RESIZE and does not clean up source host resources > Message-ID: > <cabuq5ywxw_msygeu6fxxghz+-okjajhen_ecfkmuir1arbg...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Sorry, I forgot to run 'nova resize-confirm'.... > > > On Mon, Aug 8, 2016 at 6:17 PM, Gustavo Randich <[email protected]> > wrote: > >> Hi folks, >> >> I'm using Mitaka, and when running "nova migrate <instance-uuid>", once >> the instance is migrated OK to other host, it remains forever in >> VERIFY_RESIZE status (not ACTIVE). There are no errors in the log. >> >> Also, in the source host, the directory >> /var/lib/nova/instances/<instance-uuid>_resize >> is left with disk, disk.info files, etc. in it, and the virsh domain >> remains defined (but in shut off state). >> >> Is all this expected? >> >> Thanks! >> >> Gustavo > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160808/c75e2be3/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Tue, 9 Aug 2016 00:02:14 +0200 > From: Ihar Hrachyshka <[email protected]> > To: Micha? Jastrz?bski <[email protected]> > Cc: OpenStack Operators <[email protected]> > Subject: Re: [Openstack-operators] [nova] can we lock RPC version with > upgrade_levels on neutron-openvswitch-agent ? > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8; delsp=yes; format=flowed > > (Adding back ops@) > > Micha? Jastrz?bski <[email protected]> wrote: > >> Yes, but it's a bit different. Difference being if you're doing it >> right, you can keep nova running during upgrade. Can't say the same >> for neutron. > > There is ongoing work to make it possible. The way it looks now, it will > take Ocata the least. Till that happy time, you should indeed all > controllers before upgrading database. > > That said, you can still run your agents while you upgrade your controller > nodes. Once you are done with controllers, you can upgrade one remaining > node running agents at a time. > > Ihar > > > > ------------------------------ > > Message: 3 > Date: Mon, 8 Aug 2016 17:06:34 -0500 > From: Micha? Jastrz?bski <[email protected]> > To: Ihar Hrachyshka <[email protected]> > Cc: OpenStack Operators <[email protected]> > Subject: Re: [Openstack-operators] [nova] can we lock RPC version with > upgrade_levels on neutron-openvswitch-agent ? > Message-ID: > <calc0zud1koa5d4vtzf+olr-updkinxjteeflrk5u0fogidf...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Yes, that's true, and that's what we're doing really. Our order of > upgrade is q-srv -> q-ovs-agent -> q-dhcp and rest. If that causes > issues, please submit bug for it. We should address that in our > playbooks. > >> On 8 August 2016 at 17:02, Ihar Hrachyshka <[email protected]> wrote: >> (Adding back ops@) >> >> Micha? Jastrz?bski <[email protected]> wrote: >> >>> Yes, but it's a bit different. Difference being if you're doing it >>> right, you can keep nova running during upgrade. Can't say the same >>> for neutron. >> >> >> There is ongoing work to make it possible. The way it looks now, it will >> take Ocata the least. Till that happy time, you should indeed all >> controllers before upgrading database. >> >> That said, you can still run your agents while you upgrade your controller >> nodes. Once you are done with controllers, you can upgrade one remaining >> node running agents at a time. >> >> Ihar > > > > ------------------------------ > > Message: 4 > Date: Mon, 8 Aug 2016 15:45:36 -0700 > From: Tom Fifield <[email protected]> > To: OpenStack Operators <[email protected]> > Subject: [Openstack-operators] Ops Meetups Team - Next Meeting > Coordinates and News > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8; format=flowed > > Ops Meetups Team, > > Cheers for your great work in the last meeting. We had some fantastic > discussion, and a special guest appearance from Allison Price. The > meeting overview can be found at [3]). > > > ==Next Meeting== > Unless there is further discussion, this the next meeting is at: > > ==> Tuesday, 8 of Aug at 1400 UTC[1] in #openstack-operators > > [2] will be kept up to date with information about the meeting time and > agenda > > > ==August Meetup== > NYC is tracking well. We have 83 registered so far, and have been > working on the agenda - expect to discuss that at this meeting and get a > draft on the ops ML ASAP. Then the process of finding moderators will start. > > We still need a sponsor for our evening event. Multiple companies > chipping in together would be ideal. See the email from Melvin: > > http://lists.openstack.org/pipermail/openstack-operators/2016-August/011153.html > > > > ==Meetup promotion== > We had a great discussion on meetup promotion and confirmed the list of > tasks we plan to do to promote the meetups appropriately to ensure we > get new people coming and also make sure they're cloud ops. See > Allison's summary here: > > http://lists.openstack.org/pipermail/openstack-operators/2016-August/011152.html > > > > > > > Regards, > > > Tom > > > [1] > http://www.timeanddate.com/worldclock/fixedtime.html?msg=Ops+Meetups+Team&iso=20160808T22&p1=241 > > [2] https://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information > > [3] > http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-08-02-14.00.html > > > > ------------------------------ > > Message: 5 > Date: Mon, 8 Aug 2016 15:46:48 -0700 > From: Tom Fifield <[email protected]> > To: OpenStack Operators <[email protected]> > Subject: Re: [Openstack-operators] Ops Meetups Team - Next Meeting > Coordinates and News > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8; format=flowed > > As usual, I have messed up the date. Email updated below with correct > information. > >> On ???????? ? 03:45, Tom Fifield wrote: >> Ops Meetups Team, >> >> Cheers for your great work in the last meeting. We had some fantastic >> discussion, and a special guest appearance from Allison Price. The >> meeting overview can be found at [3]). >> >> >> ==Next Meeting== >> Unless there is further discussion, this the next meeting is at: >> >> ==> Tuesday, 9 of Aug at 1400 UTC[1] in #openstack-operators >> >> [2] will be kept up to date with information about the meeting time and >> agenda >> >> >> ==August Meetup== >> NYC is tracking well. We have 83 registered so far, and have been >> working on the agenda - expect to discuss that at this meeting and get a >> draft on the ops ML ASAP. Then the process of finding moderators will >> start. >> >> We still need a sponsor for our evening event. Multiple companies >> chipping in together would be ideal. See the email from Melvin: >> >> http://lists.openstack.org/pipermail/openstack-operators/2016-August/011153.html >> >> >> >> >> ==Meetup promotion== >> We had a great discussion on meetup promotion and confirmed the list of >> tasks we plan to do to promote the meetups appropriately to ensure we >> get new people coming and also make sure they're cloud ops. See >> Allison's summary here: >> >> http://lists.openstack.org/pipermail/openstack-operators/2016-August/011152.html >> >> >> >> >> >> >> >> Regards, >> >> >> Tom >> >> >> [1] >> http://www.timeanddate.com/worldclock/fixedtime.html?msg=Ops+Meetups+Team&iso=20160809T22&p1=241 >> >> >> [2] https://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information >> >> [3] >> http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-08-02-14.00.html > > > > ------------------------------ > > Message: 6 > Date: Mon, 08 Aug 2016 17:49:48 -0500 > From: Melvin Hillsman <[email protected]> > To: Tom Fifield <[email protected]>, OpenStack Operators > <[email protected]> > Subject: Re: [Openstack-operators] Ops Meetups Team - Next Meeting > Coordinates and News > Message-ID: <[email protected]> > Content-Type: text/plain; charset="UTF-8" > > I beg to differ, it is not you, but the date that messed up! :P all is > forgiven. > > Kind regards, > -- > Melvin Hillsman > Ops Technical Lead > OpenStack Innovation Center > [email protected] > phone: (210) 312-1267 > mobile: (210) 413-1659 > Learner | Ideation | Belief | Responsibility | Command > http://osic.org > > > > > > > >> On 8/8/16, 5:46 PM, "Tom Fifield" <[email protected]> wrote: >> >> As usual, I have messed up the date. Email updated below with correct >> information. >> >>> On ???????? ? 03:45, Tom Fifield wrote: >>> Ops Meetups Team, >>> >>> Cheers for your great work in the last meeting. We had some fantastic >>> discussion, and a special guest appearance from Allison Price. The >>> meeting overview can be found at [3]). >>> >>> >>> ==Next Meeting== >>> Unless there is further discussion, this the next meeting is at: >>> >>> ==> Tuesday, 9 of Aug at 1400 UTC[1] in #openstack-operators >>> >>> [2] will be kept up to date with information about the meeting time and >>> agenda >>> >>> >>> ==August Meetup== >>> NYC is tracking well. We have 83 registered so far, and have been >>> working on the agenda - expect to discuss that at this meeting and get a >>> draft on the ops ML ASAP. Then the process of finding moderators will >>> start. >>> >>> We still need a sponsor for our evening event. Multiple companies >>> chipping in together would be ideal. See the email from Melvin: >>> >>> http://lists.openstack.org/pipermail/openstack-operators/2016-August/011153.html >>> >>> >>> >>> >>> ==Meetup promotion== >>> We had a great discussion on meetup promotion and confirmed the list of >>> tasks we plan to do to promote the meetups appropriately to ensure we >>> get new people coming and also make sure they're cloud ops. See >>> Allison's summary here: >>> >>> http://lists.openstack.org/pipermail/openstack-operators/2016-August/011152.html >>> >>> >>> >>> >>> >>> >>> >>> Regards, >>> >>> >>> Tom >>> >>> >>> [1] >>> http://www.timeanddate.com/worldclock/fixedtime.html?msg=Ops+Meetups+Team&iso=20160809T22&p1=241 >>> >>> >>> [2] https://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information >>> >>> [3] >>> http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-08-02-14.00.html >> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > ------------------------------ > > Message: 7 > Date: Tue, 9 Aug 2016 09:19:58 +0000 > From: Emilio Moreno Fernandez <[email protected]> > To: 'Pouliot.net' <[email protected]> > Cc: "'[email protected]'" > <[email protected]> > Subject: Re: [Openstack-operators] VirtIO and IDE disk > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="utf-8" > > Hi Peter, > > Drivers are correct for Windows 2012 R2, if I install one server with 2012 > ISO disk and VirtIO ISO to volume. All it?s ok! > But...if I receive one vmdk image, I convert it to raw and launch it with ide > bus on hda...but i want lauch it with virtio bus. > > Boot the instance...install virtio driver for Windows 2012 R2 of last ISO > from fedora like ?legacy hardware? and shutoff...at the next boot...BSOD of > Windows 2012. > > This process it?s ok with Windows 2008 R2, Windows XP, Windows 2003, Windows > 7 and Windows 8. > > > One solution is launch volume in my PC with KVM local install, I can launch > instance with two volumes, first IDE hda volume with system and second volume > like vdc VirtIO. When I boot system, I can install drivers for second VirtIO > volume and then I can launch system volume like VirtIO VDA without problems. > I think that Windows install driver correctly with virtio volume attached. > > > Finally, I want to launch one instance in Openstack JUNO, with two volumes, > one IDE HDA and second VirtIO like vdc for example. I can?t launch instance > like this, this is my last option because manually install of drivers on > Windows 2012 installed and migrated fail. > > Thanks > > _________________________________________________________________________ > > Emilio Moreno Fern?ndez > Departamento de Sistemas > > c/ Artesans, 7 - Parc Tecnol?gic del Vall?s > 08290 Cerdanyola del Vall?s - Barcelona > > Tel. 902 902 685 > E-mail. [email protected] > www.adam.es<http://www.adam.es/> > > [adam_linkedin]<https://www.linkedin.com/company/adam-tic> > LinkedIn<https://www.linkedin.com/company/adam-tic> | [adam_twitter] > <https://twitter.com/adam_tic> @Adam_TIC<https://twitter.com/adam_tic> > > > [adam_mail]<http://www.adam.es/> > > De: Pouliot.net [mailto:[email protected]] > Enviado el: lunes, 08 de agosto de 2016 19:05 > Para: Emilio Moreno Fernandez > CC: [email protected] > Asunto: Re: [Openstack-operators] VirtIO and IDE disk > > Sounds like you need to use the correct paravirtualization drivers for the > hypervisor you are using. I highly suggest you create the Windows vm on > that hypervisor with certified paravirtualization drivers from the vendor of > the Linux distribution you are using. > > If you have more questions, email me here: > [email protected]<mailto:[email protected]> and I'll setup a call. > > P > > On Aug 8, 2016, at 9:30 AM, Emilio Moreno Fernandez > <[email protected]<mailto:[email protected]>> wrote: > Hi all, > > We have very problems to launch Windows Server 2012 without viostor driver. > I can launch with ?hda? and install drivers but before we have BSOD on > Windows. > > It?s possible launch instance with one volume on hda and other volume with > vdc for example to install drivers without legacy software? > > How I can to resolve this with glance image of Windows imported from ESX > Server. (VirtIO drivers are in C:\ ) > > Thanks > > _________________________________________________________________________ > > Emilio Moreno Fern?ndez > Departamento de Sistemas > > c/ Artesans, 7 - Parc Tecnol?gic del Vall?s > 08290 Cerdanyola del Vall?s - Barcelona > > Tel. 902 902 685 > E-mail. [email protected]<mailto:[email protected]> > www.adam.es<http://www.adam.es/> > > <image001.png><https://www.linkedin.com/company/adam-tic> > LinkedIn<https://www.linkedin.com/company/adam-tic> | > <image002.png><https://twitter.com/adam_tic> > @Adam_TIC<https://twitter.com/adam_tic> > > > <image003.png><http://www.adam.es/> > > _______________________________________________ > OpenStack-operators mailing list > [email protected]<mailto:[email protected]> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160809/8d2fbbfc/attachment-0001.html> > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: image001.png > Type: image/png > Size: 1081 bytes > Desc: image001.png > URL: > <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160809/8d2fbbfc/attachment-0003.png> > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: image002.png > Type: image/png > Size: 1247 bytes > Desc: image002.png > URL: > <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160809/8d2fbbfc/attachment-0004.png> > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: image003.png > Type: image/png > Size: 17302 bytes > Desc: image003.png > URL: > <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160809/8d2fbbfc/attachment-0005.png> > > ------------------------------ > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > End of OpenStack-operators Digest, Vol 70, Issue 11 > *************************************************** _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
