Re: [Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News

[Melvin Hillsman]

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
mrhills...@gmail.com
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"  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=20160809T22=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
>OpenStack-operators@lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News

[Tom Fifield]

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=20160809T22=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
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News

[Tom Fifield]

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=20160808T22=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
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [nova] can we lock RPC version with upgrade_levels on neutron-openvswitch-agent ?

[Michał Jastrzębski]

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  wrote:
> (Adding back ops@)
>
> Michał Jastrzębski  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

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [nova] can we lock RPC version with upgrade_levels on neutron-openvswitch-agent ?

[Ihar Hrachyshka]

(Adding back ops@)

Michał Jastrzębski  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

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] migration leaves instance in VERIFY_RESIZE and does not clean up source host resources

[Gustavo Randich]

Sorry, I forgot to run 'nova resize-confirm'


On Mon, Aug 8, 2016 at 6:17 PM, Gustavo Randich 
wrote:

> Hi folks,
>
> I'm using Mitaka, and when running "nova migrate ", 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/_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
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Mid-Cycle Meetup, NYC, August 25th, call for additional working group sessions

[Chris Morgan]

Hello Everyone,
  The itinerary for the meet up is starting to come together nicely. We
have landed the general sessions on the main stage fairly well I feel.
However, we can fit more working group proposals into the venue but need
some more topics.

The etherpad for suggestions is here :

https://etherpad.openstack.org/p/NYC-ops-meetup

and the current state of the itinerary is here

https://docs.google.com/spreadsheets/d/1EUSYMs3GfglnD8yfFaAXWhLe0F5y9hCUKqCYe0Vp1oA/edit?pref=2=1#gid=1046944156

Please contribute by adding topics and/or +1ing existing topics. This
itinerary will be discussed in the IRC meeting tomorrow, which I believe
Tom will be sending out his handy reminder for soon.

Chris

-- 
Chris Morgan 
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [interop-challenge] [osops] [osops-tools-contrib] osops repo for heat Template

[Sun, Yih Leong]

FYI we have submitted the heat template to the osops repo and is now pending 
review at gerrit.
Would appreciate the core reviewer of osops to have a look. Thanks!
https://review.openstack.org/#/c/351799/


From: Tong Li [mailto:liton...@us.ibm.com]
Sent: Thursday, August 4, 2016 10:15 AM
To: Sun, Yih Leong >
Cc: akapa...@mirantis.com; Randal, Allison 
>; 
anni@huawei.com; Brad Topol 
>; 
bren...@mirantis.com; Barrett, Carol L 
>; Catherine Cuong 
Diep >; Brown, David L 
>; defcore-committee 
>;
 dn2...@att.com; ee5...@att.com; 
egle.sig...@rackspace.com; Evans, Eileen 
>; Elizabeth Kueper 
>; Stewart, Gretchen 
>; Janssen, Hank 
H. >; 
huangzhip...@huawei.com; Jason Kennedy 
>; Meyer, Jim 
>; Johanna Koester 
>; Woodburn, John L 
>; McRoberts, Julie 
>; 
kaneshige.ke...@jp.fujitsu.com; 
letuc...@cisco.com; 
liyon...@huawei.com; Cazares, Luz 
>; 
manju.ramanathp...@hds.com; Bonell 
Manjarrez, Marcela 
>;
 mar...@redhat.com; 
mark.ba...@canonical.com; Apostol, Michael J 
>; 
mvoel...@vmware.com; 
nij...@redhat.com; Strottman, Nissa 
>; 
pchadw...@suse.com; Yeluri, Raghuram 
>; 
rbry...@redhat.com; 
roaga...@cisco.com; 
rob.es...@netapp.com; Rochelle Grober 
>; Sodoma, Scott 
>; Shamail Tahir 
>; 
soniarv...@vmware.com; 
tf4...@att.com; Travis Mcpeak 
>; Vince Brunssen 
>
Subject: RE: [interop-challenge] osops repo for heat Template


Yih Leong,
I would say yes. I am thinking if we can simply write some bash script 
(thinking curl) to drive the test and eventually upload the results. terraform 
should allow local-exec to run bash script but I have not tested that. I am 
totally open for better methods.

Thanks.

Tong Li
IBM Open Technology
Building 501/B205
liton...@us.ibm.com

[Inactive hide details for "Sun, Yih Leong" ---08/04/2016 12:37:15 PM---That’s 
should works for now. I will get my team to uplo]"Sun, Yih Leong" ---08/04/2016 
12:37:15 PM---That’s should works for now. I will get my team to upload the 
heat template to https://github.com/op

From: "Sun, Yih Leong" >
To: Tong Li/Raleigh/IBM@IBMUS
Cc: "akapa...@mirantis.com" 
>, "Randal, Allison" 
>, 
"anni@huawei.com" 
>, Brad 
Topol/Raleigh/IBM@IBMUS, "bren...@mirantis.com" 
>, "Barrett, Carol L" 
>, Catherine Cuong 
Diep/San Jose/IBM@IBMUS, "Brown, David L" 
>, defcore-committee 
>,
 "dn2...@att.com" 
>, 

[Openstack-operators] OpenStack Developer Mailing List Digest July 23 to August 5

[Mike Perez]

http://www.openstack.org/blog/2016/08/openstack-developer-mailing-list-digest-20160805/

-- 
Mike Perez

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] VirtIO and IDE disk

[Pouliot.net]

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: openst...@microsoft.com and I'll 
setup a call.

P

> On Aug 8, 2016, at 9:30 AM, Emilio Moreno Fernandez  
> 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. emilio.mor...@adam.es
> www.adam.es
>  
>  LinkedIn  |@Adam_TIC 
>  
>  
>  
>  
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] nova resize on shared storage

[Jay Pipes]

Timofei, thanks for bringing up the resource providers work; it is 
absolutely trying to solve the problem highlighted in this post. 
Antonio, comments inline.


On 08/08/2016 05:22 AM, Antonio Messina wrote:

2016-08-08 10:52 GMT+02:00 Timofei Durakov :

Hi,

so for this moment we have 2 options:
- somehow check every time that nodes are on shared storage(now it's done
over ssh)
- define that shared storage explicitly()
The possible workaround for the first option is to use RPC for checking that
temporarily created test file exists(more RPC calls).


This sounds like a sane idea as well.


For the second option(I think the most preferable) there is a bp [1] that
introduce abstraction that allows set up such shared storages.


Please note that "shared storage" is a relation between two compute
nodes: "do we share the same storage?". In a complex enough cloud you
might have nodes with shared storage and "standalone" nodes, so you
cannot use a global config option.

The linked blueprint seems to go in the right direction (although I
could only make sense of it after reading the related spec page:
http://specs.openstack.org/openstack/nova-specs/specs/newton/approved/generic-resource-pools.html)


Please do let us know if you have questions regarding the proposed 
implementation in the spec above. We are actively working on this code 
and our goal is to have the resource tracker in Nova writing inventory 
and allocation records by the Newton release, with integrations of the 
Nova scheduler and conductor with the placement API coming in Ocata.


Best,
-jay


Alternatively we could use  an host aggregate property, like
"shared_storage=". All nodes with the same label also share the
same storage. But I personally like the resource-pool idea better.

my 2 cents.

.a.



___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] VirtIO and IDE disk

[Emilio Moreno Fernandez]

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. emilio.mor...@adam.es
www.adam.es

[adam_linkedin] 
LinkedIn  |   [adam_twitter] 
  @Adam_TIC


[adam_mail]

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [nova] can we lock RPC version with upgrade_levels on neutron-openvswitch-agent ?

[Ihar Hrachyshka]

Steven Dake (stdake)  wrote:


Saverio,

We sorted this out in Kolla with the Nova community defining the upgrade
process.  Michal (cc) led that work in the Kolla community.  I believe you
need to upgrade compute ahead of other services so the upgrade works
properly, but I'm not certain.


The last time I heard, Nova required controller first, then computes:

http://www.danplanet.com/blog/2015/06/26/upgrading-nova-to-kilo-with-minimal-downtime/

(Note the order of steps 3 and 5.)

Same is true for neutron: you upgrade controller, then compute/network node  
agents, never the other way around.


Ihar

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] nova resize on shared storage

[Antonio Messina]

2016-08-08 10:52 GMT+02:00 Timofei Durakov :
> Hi,
>
> so for this moment we have 2 options:
> - somehow check every time that nodes are on shared storage(now it's done
> over ssh)
> - define that shared storage explicitly()
> The possible workaround for the first option is to use RPC for checking that
> temporarily created test file exists(more RPC calls).

This sounds like a sane idea as well.

> For the second option(I think the most preferable) there is a bp [1] that
> introduce abstraction that allows set up such shared storages.

Please note that "shared storage" is a relation between two compute
nodes: "do we share the same storage?". In a complex enough cloud you
might have nodes with shared storage and "standalone" nodes, so you
cannot use a global config option.

The linked blueprint seems to go in the right direction (although I
could only make sense of it after reading the related spec page:
http://specs.openstack.org/openstack/nova-specs/specs/newton/approved/generic-resource-pools.html)

Alternatively we could use  an host aggregate property, like
"shared_storage=". All nodes with the same label also share the
same storage. But I personally like the resource-pool idea better.

my 2 cents.

.a.

-- 
antonio.s.mess...@gmail.com
antonio.mess...@uzh.ch +41 (0)44 635 42 22
S3IT: Service and Support for Science IT   http://www.s3it.uzh.ch/
University of Zurich
Winterthurerstrasse 190
CH-8057 Zurich Switzerland

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators