Re: [Openstack-operators] It's time...

[Lauren Sell]

Tom,

The OpenStack community is a family, and you will always be part of it. You’ve 
made a huge impact bootstrapping the User Committee, empowering operators and 
generally growing the user community. The silver lining is that you’ve also 
helped grow many new leaders in the community to help carry forward this 
important work.

We hope you stay close to OpenStack, but regardless I think you’ve officially 
achieved AUC status for life...and it sounds like we’ll have a good crew to 
cheers you in Sydney! :)

To the community,

Tom will be on board through the end of the year to help transition while we 
work to fill his shoes on the Foundation staff. In the meantime, the User 
Committee leaders are good points of contact for community organizing, and you 
can get in touch with them through the UC mailing list and regular IRC 
meetings. 

We also have quite a few members of the Foundation staff who work closely with 
the UC and across the community, including Allison Price (working with the UC 
on the User Survey & Superuser), Anne Bertucio (working with Shamail & product 
team on the Roadmap efforts), Chris Hoge (focused on testing and working across 
communities like Kubernetes), Mike Perez (cross project developer coordinator), 
Kendall Nelson (upstream development coordinator & upstream institute), Ildiko 
Vancsa (telecom, OPNFV liaison, upstream institute), Jimmy McArthur (supporting 
the Forum & AUC designation), David Flanders (working with the public cloud 
working group and “closing the app gap”) and Sonia Ramza (intern helping 
communicate with Ambassadors & user group leaders). I’ve copied them on this 
email so that their contact info is handy.

Please know we’re here and always available to serve the community, and feel 
free to reach out to me directly if you have any questions or concerns.

Cheers,
Lauren


> On Oct 4, 2017, at 9:20 AM, Tom Fifield  wrote:
> 
> Hi all,
> 
> Tom here, on a personal note.
> 
> It's quite fitting that this November our summit is in Australia :)
> 
> I'm hoping to see you there because after being part of 15 releases, and 
> travelling the equivalent of a couple of round trips to the moon to witness 
> OpenStack grow around the world, the timing is right for me to step down as 
> your Community Manager.
> 
> We've had an incredible journey together, culminating in the healthy 
> community we have today. Across more than 160 countries, users and developers 
> collaborate to make clouds better for the work that matters. The diversity of 
> use is staggering, and the scale of resources being run is quite significant. 
> We did that :)
> 
> 
> Behind the scenes, I've spent the past couple of months preparing to 
> transition various tasks to other members of the Foundation staff. If you see 
> a new name behind an openstack.org email address, please give them due 
> attention and care - they're all great people. I'll be around through to year 
> end to shepherd the process, so please ping me if you are worried about 
> anything.
> 
> Always remember, you are what makes OpenStack. OpenStack changes and thrives 
> based on how you feel and what work you do. It's been a privilege to share 
> the journey with you.
> 
> 
> 
> So, my plan? After a decade of diligent effort in organisations 
> euphemistically described as "minimally-staffed", I'm looking forward to 
> taking a decent holiday. Though, if you have a challenge interesting enough 
> to wrest someone from a tropical beach or a misty mountain top ... ;)
> 
> 
> There are a lot of you out there to whom I remain indebted. Stay in touch to 
> make sure your owed drinks make it to you!
> 
> +886 988 33 1200
> t...@tomfifield.net
> https://www.linkedin.com/in/tomfifield
> https://twitter.com/TomFifield
> 
> 
> Regards,
> 
> 
> 
> Tom
> 
> ___
> 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] It's time...

[Shintaro Mizuno]

Tom,

Thank you for everything you've done for us.

I especially would like to express my gratitude on behalf of Japan 
OpenStack User Group.
Our group wouldn't be as successful as now without your support and 
guidance.


I wish you have a good holiday and hope to see you around soon!

Cheers,
Shintaro

On 2017/10/04 23:20, Tom Fifield wrote:

Hi all,

Tom here, on a personal note.

It's quite fitting that this November our summit is in Australia :)

I'm hoping to see you there because after being part of 15 releases, and
travelling the equivalent of a couple of round trips to the moon to
witness OpenStack grow around the world, the timing is right for me to
step down as your Community Manager.

We've had an incredible journey together, culminating in the healthy
community we have today. Across more than 160 countries, users and
developers collaborate to make clouds better for the work that matters.
The diversity of use is staggering, and the scale of resources being run
is quite significant. We did that :)


Behind the scenes, I've spent the past couple of months preparing to
transition various tasks to other members of the Foundation staff. If
you see a new name behind an openstack.org email address, please give
them due attention and care - they're all great people. I'll be around
through to year end to shepherd the process, so please ping me if you
are worried about anything.

Always remember, you are what makes OpenStack. OpenStack changes and
thrives based on how you feel and what work you do. It's been a
privilege to share the journey with you.



So, my plan? After a decade of diligent effort in organisations
euphemistically described as "minimally-staffed", I'm looking forward to
taking a decent holiday. Though, if you have a challenge interesting
enough to wrest someone from a tropical beach or a misty mountain top
... ;)


There are a lot of you out there to whom I remain indebted. Stay in
touch to make sure your owed drinks make it to you!

+886 988 33 1200
t...@tomfifield.net
https://www.linkedin.com/in/tomfifield
https://twitter.com/TomFifield


Regards,



Tom

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



--
Shintaro MIZUNO (水野伸太郎)
NTT Software Innovation Center
TEL: 0422-59-4977
E-mail: mizuno.shint...@lab.ntt.co.jp

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

[Openstack-operators] Ocata The placement API endpoint not found on Ubuntu

[Divneet Singh]

Hello, I have trying to install ocata on Ubuntu 16.04 , for the time being
i have 2 nodes . just can't figure this out.

I have setup Placement API. But get error after restart nova service or
reboot

" 017-08-18 08:27:41.496 1422 WARNING nova.scheduler.client.report
[req-17911703-827e-402d-85e8-a0bb25003fe3 - - - - -] The placement API
endpoint not found. Placement is optional in Newton, but required in Ocata.
Please enable the placement service before upgrading.  "


And on the controller node when I run the command .
openstack@controller:~$ sudo nova-status  upgrade check
+---+
| Upgrade Check Results |
+---+
| Check: Cells v2   |
| Result: Success   |
| Details: None |
+---+
| Check: Placement API  |
| Result: Failure   |
| Details: Placement API endpoint not found.|
+---+
| Check: Resource Providers |
| Result: Warning   |
| Details: There are no compute resource providers in the Placement |
|   service but there are 1 compute nodes in the deployment.|
|   This means no compute nodes are reporting into the  |
|   Placement service and need to be upgraded and/or fixed. |
|   See |
|   http://docs.openstack.org/developer/nova/placement.html |
|   for more details.

I followed the the ocata guide given in the documentation by the letter .

After a feedback i got , just to make sure placement service configured in
the service catalog:
$  openstack catalog show placement
+---++
| Field | Value  |
+---++
| endpoints | RegionOne  |
|   |   admin: http://controller:8778|
|   | RegionOne  |
|   |   public: http://controller:8778   |
|   | RegionOne  |
|   |   internal: http://controller:8778 |
|   ||
| id| 825f1a56d9a4438d9f54d893a7b227c0   |
| name  | placement  |
| type  | placement  |
+---++

$ export TOKEN=$(openstack token issue -f value -c id)
$ curl -H "x-auth-token: $TOKEN" $PLACEMENT
{"versions": [{"min_version": "1.0", "max_version": "1.4", "id": "v1.0"}]}

I think this means that Placement service is configured correctly .

Do i need to configure a web server on the compute node  ?


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

Re: [Openstack-operators] It's time...

[Chris Morgan]

Thanks for everything Tom. You've made OpenStack more than something I just
happen to be doing, for me and for many others. Far from you needing to buy
us beers, I'd say the opposite is true!

Chris

On Wed, Oct 4, 2017 at 12:19 PM,  wrote:

> Tom,
>
> Thank you for everything.
>
> Arkady
>
>
>
> *From:* Rico Lin [mailto:rico.lin.gua...@gmail.com]
> *Sent:* Wednesday, October 04, 2017 9:45 AM
> *To:* Tom Fifield 
> *Cc:* OpenStack Operators 
> *Subject:* Re: [Openstack-operators] It's time...
>
>
>
> Tom,
>
>
>
> It's my pleasure to working with you and learning from you.
> Thank you for what you have done for the community and open source.
> Hopefully we will have chances to work together in future, and of course,
> see you in Sydney!
>
>
>
>
>
> 2017-10-04 22:34 GMT+08:00 Tim Bell :
>
> Tom,
>
> All the best for the future. I will happily share a beverage or two in
> Sydney, reflect on the early days and toast the growth of the community
> that you have been a major contributor to.
>
> Tim
>
>
> -Original Message-
> From: Tom Fifield 
> Date: Wednesday, 4 October 2017 at 16:25
> To: openstack-operators 
> Subject: [Openstack-operators] It's time...
>
> Hi all,
>
> Tom here, on a personal note.
>
> It's quite fitting that this November our summit is in Australia :)
>
> I'm hoping to see you there because after being part of 15 releases,
> and
> travelling the equivalent of a couple of round trips to the moon to
> witness OpenStack grow around the world, the timing is right for me to
> step down as your Community Manager.
>
> We've had an incredible journey together, culminating in the healthy
> community we have today. Across more than 160 countries, users and
> developers collaborate to make clouds better for the work that matters.
> The diversity of use is staggering, and the scale of resources being
> run
> is quite significant. We did that :)
>
>
> Behind the scenes, I've spent the past couple of months preparing to
> transition various tasks to other members of the Foundation staff. If
> you see a new name behind an openstack.org email address, please give
> them due attention and care - they're all great people. I'll be around
> through to year end to shepherd the process, so please ping me if you
> are worried about anything.
>
> Always remember, you are what makes OpenStack. OpenStack changes and
> thrives based on how you feel and what work you do. It's been a
> privilege to share the journey with you.
>
>
>
> So, my plan? After a decade of diligent effort in organisations
> euphemistically described as "minimally-staffed", I'm looking forward
> to
> taking a decent holiday. Though, if you have a challenge interesting
> enough to wrest someone from a tropical beach or a misty mountain top
> ... ;)
>
>
> There are a lot of you out there to whom I remain indebted. Stay in
> touch to make sure your owed drinks make it to you!
>
> +886 988 33 1200
> t...@tomfifield.net
> https://www.linkedin.com/in/tomfifield
> https://twitter.com/TomFifield
>
>
> Regards,
>
>
>
> Tom
>
> ___
> 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
>
>
>
>
>
> --
>
> May The Force of OpenStack Be With You,
>
> *Rico Lin *irc: ricolin
>
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>


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

Re: [Openstack-operators] It's time...

[Shamail Tahir]

Hi Tom,

Thank you for everything that you have contributed to the community and for the 
time/energy you invested in helping the project and our global user communities 
grow to tremendous heights.

I also want to sincerely thank you for the personal impact you’ve had on my 
path within the community and general guidance throughout the years.

You will be sorely missed and I echo the others when I say that we hope to see 
you around.

I won’t be around Sydney so I’m hoping we get a future opportunity to share 
some Moscow mules and trade stories. I would be disappointed if our paths 
didn’t cross again!

Continue fighting for the users in your future endeavors.

Take care,
Shamail 

> On Oct 4, 2017, at 10:20 AM, Tom Fifield  wrote:
> 
> Hi all,
> 
> Tom here, on a personal note.
> 
> It's quite fitting that this November our summit is in Australia :)
> 
> I'm hoping to see you there because after being part of 15 releases, and 
> travelling the equivalent of a couple of round trips to the moon to witness 
> OpenStack grow around the world, the timing is right for me to step down as 
> your Community Manager.
> 
> We've had an incredible journey together, culminating in the healthy 
> community we have today. Across more than 160 countries, users and developers 
> collaborate to make clouds better for the work that matters. The diversity of 
> use is staggering, and the scale of resources being run is quite significant. 
> We did that :)
> 
> 
> Behind the scenes, I've spent the past couple of months preparing to 
> transition various tasks to other members of the Foundation staff. If you see 
> a new name behind an openstack.org email address, please give them due 
> attention and care - they're all great people. I'll be around through to year 
> end to shepherd the process, so please ping me if you are worried about 
> anything.
> 
> Always remember, you are what makes OpenStack. OpenStack changes and thrives 
> based on how you feel and what work you do. It's been a privilege to share 
> the journey with you.
> 
> 
> 
> So, my plan? After a decade of diligent effort in organisations 
> euphemistically described as "minimally-staffed", I'm looking forward to 
> taking a decent holiday. Though, if you have a challenge interesting enough 
> to wrest someone from a tropical beach or a misty mountain top ... ;)
> 
> 
> There are a lot of you out there to whom I remain indebted. Stay in touch to 
> make sure your owed drinks make it to you!
> 
> +886 988 33 1200
> t...@tomfifield.net
> https://www.linkedin.com/in/tomfifield
> https://twitter.com/TomFifield
> 
> 
> Regards,
> 
> 
> 
> Tom
> 
> ___
> 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] It's time...

[Arkady.Kanevsky]

Tom,
Thank you for everything.
Arkady

From: Rico Lin [mailto:rico.lin.gua...@gmail.com]
Sent: Wednesday, October 04, 2017 9:45 AM
To: Tom Fifield 
Cc: OpenStack Operators 
Subject: Re: [Openstack-operators] It's time...

Tom,

It's my pleasure to working with you and learning from you.
Thank you for what you have done for the community and open source.
Hopefully we will have chances to work together in future, and of course, see 
you in Sydney!


2017-10-04 22:34 GMT+08:00 Tim Bell mailto:tim.b...@cern.ch>>:
Tom,

All the best for the future. I will happily share a beverage or two in Sydney, 
reflect on the early days and toast the growth of the community that you have 
been a major contributor to.

Tim

-Original Message-
From: Tom Fifield mailto:t...@openstack.org>>
Date: Wednesday, 4 October 2017 at 16:25
To: openstack-operators 
mailto:openstack-operators@lists.openstack.org>>
Subject: [Openstack-operators] It's time...

Hi all,

Tom here, on a personal note.

It's quite fitting that this November our summit is in Australia :)

I'm hoping to see you there because after being part of 15 releases, and
travelling the equivalent of a couple of round trips to the moon to
witness OpenStack grow around the world, the timing is right for me to
step down as your Community Manager.

We've had an incredible journey together, culminating in the healthy
community we have today. Across more than 160 countries, users and
developers collaborate to make clouds better for the work that matters.
The diversity of use is staggering, and the scale of resources being run
is quite significant. We did that :)


Behind the scenes, I've spent the past couple of months preparing to
transition various tasks to other members of the Foundation staff. If
you see a new name behind an openstack.org email 
address, please give
them due attention and care - they're all great people. I'll be around
through to year end to shepherd the process, so please ping me if you
are worried about anything.

Always remember, you are what makes OpenStack. OpenStack changes and
thrives based on how you feel and what work you do. It's been a
privilege to share the journey with you.



So, my plan? After a decade of diligent effort in organisations
euphemistically described as "minimally-staffed", I'm looking forward to
taking a decent holiday. Though, if you have a challenge interesting
enough to wrest someone from a tropical beach or a misty mountain top ... ;)


There are a lot of you out there to whom I remain indebted. Stay in
touch to make sure your owed drinks make it to you!

+886 988 33 1200
t...@tomfifield.net
https://www.linkedin.com/in/tomfifield
https://twitter.com/TomFifield


Regards,



Tom

___
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



--
May The Force of OpenStack Be With You,
Rico Lin
irc: ricolin




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

Re: [Openstack-operators] [nova] Should we allow passing new user_data during rebuild?

[Belmiro Moreira]

In our cloud rebuild is the only way for a user to keep the same IP.
Unfortunately, we don't offer floating IPs, yet.
Also, we use the user_data to bootstrap some actions in new instances
(puppet, ...).
Considering all the use-cases for rebuild it would be great if the
user_data can be updated at rebuild time.

On Wed, Oct 4, 2017 at 5:15 PM, Chris Friesen 
wrote:

> On 10/03/2017 11:12 AM, Clint Byrum wrote:
>
> My personal opinion is that rebuild is an anti-pattern for cloud, and
>> should be frozen and deprecated. It does nothing but complicate Nova
>> and present challenges for scaling.
>>
>> That said, if it must stay as a feature, I don't think updating the
>> user_data should be a priority. At that point, you've basically created an
>> entirely new server, and you can already do that by creating an entirely
>> new server.
>>
>
> If you've got a whole heat stack with multiple resources, and you realize
> that you messed up one thing in the template and one of your servers has
> the wrong personality/user_data, it can be useful to be able to rebuild
> that one server without affecting anything else in the stack.  That's just
> a convenience though.
>
> Chris
>
>
>
> ___
> 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] OSA upgrading Ubuntu14.04 Newton to Ubuntu16.04 Ocata

[Amy Marrich]

Grant,

Feel free to stop in even if it goes perfectly to let us know.:)

Amy (spotz)

On Wed, Oct 4, 2017 at 10:03 AM, Grant Morley 
wrote:

> Hi Amy,
>
> Many thanks for this, pleased to know that it is doable :) - We will test
> this on our dev environment first to see if there are any issues or not.
>
> Will be sure to join the #openstack-ansible channel if we get stuck.
>
> Thanks again,
>
> Grant
>
> On 04/10/17 15:56, Amy Marrich wrote:
>
> Hi Grant,
>
> We actually have the process documented here:
>
> https://etherpad.openstack.org/p/osa-newton-xenial-upgrade
>
> It does make a few assumptions so make sure you meet them before starting.
> Please join us on Freenode in the #openstack-ansible channel and we'll give
> you a hand if we can.
>
> Thanks,
>
> Amy (spotz)
>
> On Wed, Oct 4, 2017 at 9:42 AM, Grant Morley 
> wrote:
>
>> Hi All,
>>
>> Just have a quick question regarding upgrading from Newton to Ocata using
>> OSA. We have a small installation ( 4 compute. 3 management, 2 network and
>> some Ceph storage nodes ) And we are looking to upgrade from Ubuntu 14.04
>> Newton to Ubuntu 16.04  Ocata.
>>
>> Does anyone have any good tips on how to do this at all? We are not sure
>> whether it is best to decommission a single node at a time, upgrade that to
>> Ubuntu 16.04 and then get Ocata installed onto that. Or whether there is a
>> better method at all?
>>
>> We are conscious that if we bootstrap our ansible deployer machine for
>> Ocata, it will then not be able to manage the nodes that are running 14.04
>> Newton we assume?
>>
>> Another thing we were thinking was to possibly get some more kit and just
>> install Ocata from scratch on that and start to migrate customers over, but
>> again we assume would need a separate deployer to do so?.
>>
>> We would prefer to be able to upgrade both the OS for Ubuntu and
>> Openstack to Ocata using our current set up and just wondered if this was
>> even possible with OSA? Unfortunately we do not have the budget to simply
>> keep on getting more and more kit, so we have to be quite tactile about how
>> we do things.
>>
>> We are going to test this on our dev environment and see what breaks, but
>> just wondered if anyone here has come across this already and suffered the
>> pain :)
>>
>> Any suggestions would be much appreciated.
>>
>> Many thanks,
>> --
>> Grant Morley
>> Senior Cloud Engineer
>> Absolute DevOps Ltd
>> Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
>> www.absolutedevops.io gr...@absolutedevops.io 0845 874 0580
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
> --
> Grant Morley
> Senior Cloud Engineer
> Absolute DevOps Ltd
> Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
> www.absolutedevops.io gr...@absolutedevops.io 0845 874 0580
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] It's time...

[Edgar Magana]

Tom,

Thank you for your hard work in the community, your help made possible to build 
such a great community. Wow, you did travel all around and a good long break is 
for sure totally deserved.
Do not disappear, you cannot do that to us. There are so many other adventures 
that we would love to enjoy having you around.

The best wishes my friend,

Edgar

On 10/4/17, 7:20 AM, "Tom Fifield"  wrote:

Hi all,

Tom here, on a personal note.

It's quite fitting that this November our summit is in Australia :)

I'm hoping to see you there because after being part of 15 releases, and 
travelling the equivalent of a couple of round trips to the moon to 
witness OpenStack grow around the world, the timing is right for me to 
step down as your Community Manager.

We've had an incredible journey together, culminating in the healthy 
community we have today. Across more than 160 countries, users and 
developers collaborate to make clouds better for the work that matters. 
The diversity of use is staggering, and the scale of resources being run 
is quite significant. We did that :)


Behind the scenes, I've spent the past couple of months preparing to 
transition various tasks to other members of the Foundation staff. If 
you see a new name behind an openstack.org email address, please give 
them due attention and care - they're all great people. I'll be around 
through to year end to shepherd the process, so please ping me if you 
are worried about anything.

Always remember, you are what makes OpenStack. OpenStack changes and 
thrives based on how you feel and what work you do. It's been a 
privilege to share the journey with you.



So, my plan? After a decade of diligent effort in organisations 
euphemistically described as "minimally-staffed", I'm looking forward to 
taking a decent holiday. Though, if you have a challenge interesting 
enough to wrest someone from a tropical beach or a misty mountain top ... ;)


There are a lot of you out there to whom I remain indebted. Stay in 
touch to make sure your owed drinks make it to you!

+886 988 33 1200
t...@tomfifield.net

https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_in_tomfifield&d=DwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=MxltKfH_OcRFekhvqJmmY3-vVfGaJH12bZK27GB8MbU&s=P2_SpRNKx6QdEY2JNgZSL5GKfi_kr4PPUt_CCjuEu74&e=

https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_TomFifield&d=DwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=MxltKfH_OcRFekhvqJmmY3-vVfGaJH12bZK27GB8MbU&s=PeAFRbu0_X-pERcas4h4_8Oqs2_27_-C8M9PIK0y5HA&e=


Regards,



Tom

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org

https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DwIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=MxltKfH_OcRFekhvqJmmY3-vVfGaJH12bZK27GB8MbU&s=i8pZlByIXepqx0ZRMfaErKrLD8IA6VTqRB6mpAN_SuI&e=


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

Re: [Openstack-operators] [nova] Should we allow passing new user_data during rebuild?

[Chris Friesen]

On 10/03/2017 11:12 AM, Clint Byrum wrote:


My personal opinion is that rebuild is an anti-pattern for cloud, and
should be frozen and deprecated. It does nothing but complicate Nova
and present challenges for scaling.

That said, if it must stay as a feature, I don't think updating the
user_data should be a priority. At that point, you've basically created an
entirely new server, and you can already do that by creating an entirely
new server.


If you've got a whole heat stack with multiple resources, and you realize that 
you messed up one thing in the template and one of your servers has the wrong 
personality/user_data, it can be useful to be able to rebuild that one server 
without affecting anything else in the stack.  That's just a convenience though.


Chris


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

Re: [Openstack-operators] OSA upgrading Ubuntu14.04 Newton to Ubuntu16.04 Ocata

[Grant Morley]

Hi Amy,

Many thanks for this, pleased to know that it is doable :) - We will 
test this on our dev environment first to see if there are any issues or 
not.


Will be sure to join the #openstack-ansible channel if we get stuck.

Thanks again,

Grant


On 04/10/17 15:56, Amy Marrich wrote:

Hi Grant,

We actually have the process documented here:

https://etherpad.openstack.org/p/osa-newton-xenial-upgrade

It does make a few assumptions so make sure you meet them before 
starting. Please join us on Freenode in the #openstack-ansible channel 
and we'll give you a hand if we can.


Thanks,

Amy (spotz)

On Wed, Oct 4, 2017 at 9:42 AM, Grant Morley > wrote:


Hi All,

Just have a quick question regarding upgrading from Newton to
Ocata using OSA. We have a small installation ( 4 compute. 3
management, 2 network and some Ceph storage nodes ) And we are
looking to upgrade from Ubuntu 14.04 Newton to Ubuntu 16.04  Ocata.

Does anyone have any good tips on how to do this at all? We are
not sure whether it is best to decommission a single node at a
time, upgrade that to Ubuntu 16.04 and then get Ocata installed
onto that. Or whether there is a better method at all?

We are conscious that if we bootstrap our ansible deployer machine
for Ocata, it will then not be able to manage the nodes that are
running 14.04 Newton we assume?

Another thing we were thinking was to possibly get some more kit
and just install Ocata from scratch on that and start to migrate
customers over, but again we assume would need a separate deployer
to do so?.

We would prefer to be able to upgrade both the OS for Ubuntu and
Openstack to Ocata using our current set up and just wondered if
this was even possible with OSA? Unfortunately we do not have the
budget to simply keep on getting more and more kit, so we have to
be quite tactile about how we do things.

We are going to test this on our dev environment and see what
breaks, but just wondered if anyone here has come across this
already and suffered the pain :)

Any suggestions would be much appreciated.

Many thanks,

-- 
Grant Morley

Senior Cloud Engineer
Absolute DevOps Ltd
Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
www.absolutedevops.io 
gr...@absolutedevops.io  0845 874
0580

___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators





--
Grant Morley
Senior Cloud Engineer
Absolute DevOps Ltd
Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
www.absolutedevops.io  
gr...@absolutedevops.io  0845 874 0580
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] OSA upgrading Ubuntu14.04 Newton to Ubuntu16.04 Ocata

[Amy Marrich]

Hi Grant,

We actually have the process documented here:

https://etherpad.openstack.org/p/osa-newton-xenial-upgrade

It does make a few assumptions so make sure you meet them before starting.
Please join us on Freenode in the #openstack-ansible channel and we'll give
you a hand if we can.

Thanks,

Amy (spotz)

On Wed, Oct 4, 2017 at 9:42 AM, Grant Morley 
wrote:

> Hi All,
>
> Just have a quick question regarding upgrading from Newton to Ocata using
> OSA. We have a small installation ( 4 compute. 3 management, 2 network and
> some Ceph storage nodes ) And we are looking to upgrade from Ubuntu 14.04
> Newton to Ubuntu 16.04  Ocata.
>
> Does anyone have any good tips on how to do this at all? We are not sure
> whether it is best to decommission a single node at a time, upgrade that to
> Ubuntu 16.04 and then get Ocata installed onto that. Or whether there is a
> better method at all?
>
> We are conscious that if we bootstrap our ansible deployer machine for
> Ocata, it will then not be able to manage the nodes that are running 14.04
> Newton we assume?
>
> Another thing we were thinking was to possibly get some more kit and just
> install Ocata from scratch on that and start to migrate customers over, but
> again we assume would need a separate deployer to do so?.
>
> We would prefer to be able to upgrade both the OS for Ubuntu and Openstack
> to Ocata using our current set up and just wondered if this was even
> possible with OSA? Unfortunately we do not have the budget to simply keep
> on getting more and more kit, so we have to be quite tactile about how we
> do things.
>
> We are going to test this on our dev environment and see what breaks, but
> just wondered if anyone here has come across this already and suffered the
> pain :)
>
> Any suggestions would be much appreciated.
>
> Many thanks,
> --
> Grant Morley
> Senior Cloud Engineer
> Absolute DevOps Ltd
> Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
> www.absolutedevops.io gr...@absolutedevops.io 0845 874 0580
>
> ___
> 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] It's time...

[Jonathan Proulx]

You've done amazing things for OpenStack can't wait to see what amzing
thing you do next.

If I'd known sooner would have agreed to 60hrs of cattle class travel
to see you off...unfortunately as it is I won't be in Sydney.  I do
sincerely hope our paths cross again.

All the best,
-Jon

On Wed, Oct 04, 2017 at 10:20:57PM +0800, Tom Fifield wrote:
:Hi all,
:
:Tom here, on a personal note.
:
:It's quite fitting that this November our summit is in Australia :)
:
:I'm hoping to see you there because after being part of 15 releases, and
:travelling the equivalent of a couple of round trips to the moon to witness
:OpenStack grow around the world, the timing is right for me to step down as
:your Community Manager.
:
:We've had an incredible journey together, culminating in the healthy
:community we have today. Across more than 160 countries, users and developers
:collaborate to make clouds better for the work that matters. The diversity of
:use is staggering, and the scale of resources being run is quite significant.
:We did that :)
:
:
:Behind the scenes, I've spent the past couple of months preparing to
:transition various tasks to other members of the Foundation staff. If you see
:a new name behind an openstack.org email address, please give them due
:attention and care - they're all great people. I'll be around through to year
:end to shepherd the process, so please ping me if you are worried about
:anything.
:
:Always remember, you are what makes OpenStack. OpenStack changes and thrives
:based on how you feel and what work you do. It's been a privilege to share
:the journey with you.
:
:
:
:So, my plan? After a decade of diligent effort in organisations
:euphemistically described as "minimally-staffed", I'm looking forward to
:taking a decent holiday. Though, if you have a challenge interesting enough
:to wrest someone from a tropical beach or a misty mountain top ... ;)
:
:
:There are a lot of you out there to whom I remain indebted. Stay in touch to
:make sure your owed drinks make it to you!
:
:+886 988 33 1200
:t...@tomfifield.net
:https://www.linkedin.com/in/tomfifield
:https://twitter.com/TomFifield
:
:
:Regards,
:
:
:
:Tom
:
:___
: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] It's time...

[Erik McCormick]

Tom,

Thank you for all you've done herding cats around here. We wouldn't be
where we are today without you. We better find a very large pub in
Sydney. See you there!

All the best on your future sunbathing endeavors :)

Cheers,
Erik

On Wed, Oct 4, 2017 at 10:20 AM, Tom Fifield  wrote:
> Hi all,
>
> Tom here, on a personal note.
>
> It's quite fitting that this November our summit is in Australia :)
>
> I'm hoping to see you there because after being part of 15 releases, and
> travelling the equivalent of a couple of round trips to the moon to witness
> OpenStack grow around the world, the timing is right for me to step down as
> your Community Manager.
>
> We've had an incredible journey together, culminating in the healthy
> community we have today. Across more than 160 countries, users and
> developers collaborate to make clouds better for the work that matters. The
> diversity of use is staggering, and the scale of resources being run is
> quite significant. We did that :)
>
>
> Behind the scenes, I've spent the past couple of months preparing to
> transition various tasks to other members of the Foundation staff. If you
> see a new name behind an openstack.org email address, please give them due
> attention and care - they're all great people. I'll be around through to
> year end to shepherd the process, so please ping me if you are worried about
> anything.
>
> Always remember, you are what makes OpenStack. OpenStack changes and thrives
> based on how you feel and what work you do. It's been a privilege to share
> the journey with you.
>
>
>
> So, my plan? After a decade of diligent effort in organisations
> euphemistically described as "minimally-staffed", I'm looking forward to
> taking a decent holiday. Though, if you have a challenge interesting enough
> to wrest someone from a tropical beach or a misty mountain top ... ;)
>
>
> There are a lot of you out there to whom I remain indebted. Stay in touch to
> make sure your owed drinks make it to you!
>
> +886 988 33 1200
> t...@tomfifield.net
> https://www.linkedin.com/in/tomfifield
> https://twitter.com/TomFifield
>
>
> Regards,
>
>
>
> Tom
>
> ___
> 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] It's time...

[Rico Lin]

Tom,

It's my pleasure to working with you and learning from you.
Thank you for what you have done for the community and open source.
Hopefully we will have chances to work together in future, and of course,
see you in Sydney!


2017-10-04 22:34 GMT+08:00 Tim Bell :

> Tom,
>
> All the best for the future. I will happily share a beverage or two in
> Sydney, reflect on the early days and toast the growth of the community
> that you have been a major contributor to.
>
> Tim
>
> -Original Message-
> From: Tom Fifield 
> Date: Wednesday, 4 October 2017 at 16:25
> To: openstack-operators 
> Subject: [Openstack-operators] It's time...
>
> Hi all,
>
> Tom here, on a personal note.
>
> It's quite fitting that this November our summit is in Australia :)
>
> I'm hoping to see you there because after being part of 15 releases,
> and
> travelling the equivalent of a couple of round trips to the moon to
> witness OpenStack grow around the world, the timing is right for me to
> step down as your Community Manager.
>
> We've had an incredible journey together, culminating in the healthy
> community we have today. Across more than 160 countries, users and
> developers collaborate to make clouds better for the work that matters.
> The diversity of use is staggering, and the scale of resources being
> run
> is quite significant. We did that :)
>
>
> Behind the scenes, I've spent the past couple of months preparing to
> transition various tasks to other members of the Foundation staff. If
> you see a new name behind an openstack.org email address, please give
> them due attention and care - they're all great people. I'll be around
> through to year end to shepherd the process, so please ping me if you
> are worried about anything.
>
> Always remember, you are what makes OpenStack. OpenStack changes and
> thrives based on how you feel and what work you do. It's been a
> privilege to share the journey with you.
>
>
>
> So, my plan? After a decade of diligent effort in organisations
> euphemistically described as "minimally-staffed", I'm looking forward
> to
> taking a decent holiday. Though, if you have a challenge interesting
> enough to wrest someone from a tropical beach or a misty mountain top
> ... ;)
>
>
> There are a lot of you out there to whom I remain indebted. Stay in
> touch to make sure your owed drinks make it to you!
>
> +886 988 33 1200
> t...@tomfifield.net
> https://www.linkedin.com/in/tomfifield
> https://twitter.com/TomFifield
>
>
> Regards,
>
>
>
> Tom
>
> ___
> 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
>



-- 
May The Force of OpenStack Be With You,

*Rico Lin*irc: ricolin
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] OSA upgrading Ubuntu14.04 Newton to Ubuntu16.04 Ocata

[Grant Morley]

Hi All,

Just have a quick question regarding upgrading from Newton to Ocata 
using OSA. We have a small installation ( 4 compute. 3 management, 2 
network and some Ceph storage nodes ) And we are looking to upgrade from 
Ubuntu 14.04 Newton to Ubuntu 16.04 Ocata.


Does anyone have any good tips on how to do this at all? We are not sure 
whether it is best to decommission a single node at a time, upgrade that 
to Ubuntu 16.04 and then get Ocata installed onto that. Or whether there 
is a better method at all?


We are conscious that if we bootstrap our ansible deployer machine for 
Ocata, it will then not be able to manage the nodes that are running 
14.04 Newton we assume?


Another thing we were thinking was to possibly get some more kit and 
just install Ocata from scratch on that and start to migrate customers 
over, but again we assume would need a separate deployer to do so?.


We would prefer to be able to upgrade both the OS for Ubuntu and 
Openstack to Ocata using our current set up and just wondered if this 
was even possible with OSA? Unfortunately we do not have the budget to 
simply keep on getting more and more kit, so we have to be quite tactile 
about how we do things.


We are going to test this on our dev environment and see what breaks, 
but just wondered if anyone here has come across this already and 
suffered the pain :)


Any suggestions would be much appreciated.

Many thanks,

--
Grant Morley
Senior Cloud Engineer
Absolute DevOps Ltd
Units H, J & K, Gateway 1000, Whittle Way, Stevenage, Herts, SG1 2FP
www.absolutedevops.io  
gr...@absolutedevops.io  0845 874 0580
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] It's time...

[Tim Bell]

Tom,

All the best for the future. I will happily share a beverage or two in Sydney, 
reflect on the early days and toast the growth of the community that you have 
been a major contributor to.

Tim

-Original Message-
From: Tom Fifield 
Date: Wednesday, 4 October 2017 at 16:25
To: openstack-operators 
Subject: [Openstack-operators] It's time...

Hi all,

Tom here, on a personal note.

It's quite fitting that this November our summit is in Australia :)

I'm hoping to see you there because after being part of 15 releases, and 
travelling the equivalent of a couple of round trips to the moon to 
witness OpenStack grow around the world, the timing is right for me to 
step down as your Community Manager.

We've had an incredible journey together, culminating in the healthy 
community we have today. Across more than 160 countries, users and 
developers collaborate to make clouds better for the work that matters. 
The diversity of use is staggering, and the scale of resources being run 
is quite significant. We did that :)


Behind the scenes, I've spent the past couple of months preparing to 
transition various tasks to other members of the Foundation staff. If 
you see a new name behind an openstack.org email address, please give 
them due attention and care - they're all great people. I'll be around 
through to year end to shepherd the process, so please ping me if you 
are worried about anything.

Always remember, you are what makes OpenStack. OpenStack changes and 
thrives based on how you feel and what work you do. It's been a 
privilege to share the journey with you.



So, my plan? After a decade of diligent effort in organisations 
euphemistically described as "minimally-staffed", I'm looking forward to 
taking a decent holiday. Though, if you have a challenge interesting 
enough to wrest someone from a tropical beach or a misty mountain top ... ;)


There are a lot of you out there to whom I remain indebted. Stay in 
touch to make sure your owed drinks make it to you!

+886 988 33 1200
t...@tomfifield.net
https://www.linkedin.com/in/tomfifield
https://twitter.com/TomFifield


Regards,



Tom

___
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

[Openstack-operators] It's time...

[Tom Fifield]

Hi all,

Tom here, on a personal note.

It's quite fitting that this November our summit is in Australia :)

I'm hoping to see you there because after being part of 15 releases, and 
travelling the equivalent of a couple of round trips to the moon to 
witness OpenStack grow around the world, the timing is right for me to 
step down as your Community Manager.


We've had an incredible journey together, culminating in the healthy 
community we have today. Across more than 160 countries, users and 
developers collaborate to make clouds better for the work that matters. 
The diversity of use is staggering, and the scale of resources being run 
is quite significant. We did that :)



Behind the scenes, I've spent the past couple of months preparing to 
transition various tasks to other members of the Foundation staff. If 
you see a new name behind an openstack.org email address, please give 
them due attention and care - they're all great people. I'll be around 
through to year end to shepherd the process, so please ping me if you 
are worried about anything.


Always remember, you are what makes OpenStack. OpenStack changes and 
thrives based on how you feel and what work you do. It's been a 
privilege to share the journey with you.




So, my plan? After a decade of diligent effort in organisations 
euphemistically described as "minimally-staffed", I'm looking forward to 
taking a decent holiday. Though, if you have a challenge interesting 
enough to wrest someone from a tropical beach or a misty mountain top ... ;)



There are a lot of you out there to whom I remain indebted. Stay in 
touch to make sure your owed drinks make it to you!


+886 988 33 1200
t...@tomfifield.net
https://www.linkedin.com/in/tomfifield
https://twitter.com/TomFifield


Regards,



Tom

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

[Openstack-operators] [openstack-dev][all][heat] Removal of CloudWatch api

[Rico Lin]

Add OpenStack ops ML
-- Forwarded message --
From: Rabi Mishra 
Date: 2017-10-04 18:47 GMT+08:00
Subject: [openstack-dev] [heat] Removal of CloudWatch api
To: "OpenStack Development Mailing List (not for usage questions)" <
openstack-...@lists.openstack.org>


Hi All,

As discussed in the last meeting, here is the ML thead to gather more
feedback on this.

Background:

Heat support for AWS CloudWatch compatible API (a very minimalistic
implementation, primarily used for metric data collection for autoscaling,
before the telemetry services in OpenStack), has been deprecated since
Havana cycle (may be before that?).  We now have a global alias[1] for
AWS::CloudWatch::Alarm to use OS::Aodh::Alarm instead.  However, the
ability to push metrics to ceilometer via heat, using a pre-signed url for
CloudWatch api endpoint, is still supported for backward compatibility.
heat-cfntools/cfn-push-stats tool is mainly used from the instances/vms for
this.

What we plan to do?

We think that CloudWatch api  and related code base has been in heat tree
without any change for the sole reason above and possibly it's time to
remove them completely. However, we may not have an alternate way to
continue providing backward compatibility to users.

What would be the impact?

- Users using AWS::CloudWatch::Alarm and pushing metric data from instances
using cfn-push-stats would not be able to do so. Templates with these would
not work any more.

- AWS::ElasticLoadBalancing::LoadBalancer[2] resource which uses
AWS::CloudWatch::Alarm and cfn-push-stats would not work anymore. We
probably have to remove this resource too?

Though it seems like a big change, the general opinion is that there would
not be many users still using them and hence very little risk in removing
CloudWatch support completely this cycle.

If you think otherwise please let us know:)


[1] https://git.openstack.org/cgit/openstack/heat/tree/etc/heat/
environment.d/default.yaml#n6
[2] https://git.openstack.org/cgit/openstack/heat/tree/heat/
engine/resources/aws/lb/loadbalancer.py#n640

Regards,
Rabi Mishra

__
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




-- 
May The Force of OpenStack Be With You,

*Rico Lin*irc: ricolin
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators