[Openstack-operators] [tags] Meeting cancelled for 4/14 (see details for ops meetup session)

[Shamail Tahir]

Hi everyone,

The ops-tags team meeting will be cancelled for tomorrow since the team
will be meeting for a double session during the ops meetup at the OpenStack
Summit in Austin.  All are invited to participate and we look forward to
seeing you there!

Details:
https://etherpad.openstack.org/p/AUS-ops-Ops-tags

-- 
Thanks,
Shamail Tahir
t: @ShamailXD
tz: Eastern Time
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [puppet] TelemetryAlarming api.baremetal.admin.test_drivers test failed

[Emilien Macchi]

Could you please show your manifests?

I suspect keystone is not up...

---
Emilien Macchi
On Apr 12, 2016 5:23 PM, "Rayson Ho"  wrote:

> Hi,
>
> I am getting the following error when I was installing using the Puppet
> manifest.
>
> ==
> Failed 1 tests - output below:
> ==
>
>
> tempest.scenario.test_dashboard_basic_ops.TestDashboardBasicOps.test_basic_scenario[dashboard,id-4f8851b1-0e69-482b-b63b-84c6e76f6c80]
>
> --
>
> Captured traceback:
> ~~~
> Traceback (most recent call last):
>   File "tempest/test.py", line 113, in wrapper
> return f(self, *func_args, **func_kwargs)
>   File "tempest/scenario/test_dashboard_basic_ops.py", line 118, in
> test_basic_scenario
> self.check_login_page()
>   File "tempest/scenario/test_dashboard_basic_ops.py", line 82, in
> check_login_page
> self.assertIn("id_username", response.read())
>   File
> "/tmp/openstack/tempest/.tox/all-plugin/lib/python2.7/site-packages/testtools/testcase.py",
> line 368, in assertIn
> self.assertThat(haystack, Contains(needle), message)
>   File
> "/tmp/openstack/tempest/.tox/all-plugin/lib/python2.7/site-packages/testtools/testcase.py",
> line 447, in assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: 'id_username' not in
> '\n\n \n
>  Index of /\n \n \nIndex of /\n
>  \nalt="[ICO]">Name href="?C=M;O=A">Last modified href="?C=S;O=A">Size href="?C=D;O=A">Description\ncolspan="5">\ncolspan="5">\n\n\n'
>
>
> Seems like the test case is trying to find id_username from the dashboard
> page, which on the machine is:
>
> [root@node0 puppet-openstack-integration]# wget 127.0.0.1
> --2016-04-12 18:19:52--  http://127.0.0.1/
> Connecting to 127.0.0.1:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 481 [text/html]
> Saving to: ‘index.html’
>
> 100%[>]
> 481 --.-K/s   in 0s
>
> 2016-04-12 18:19:52 (15.1 MB/s) - ‘index.html’ saved [481/481]
>
> [root@node0 puppet-openstack-integration]# cat index.html
> 
> 
>  
>   Index of /
>  
>  
> Index of /
>   
> alt="[ICO]">Name href="?C=M;O=A">Last modified href="?C=S;O=A">Size href="?C=D;O=A">Description
>
>
> 
> 
>
>
> So is it an issue with Horizon as it is not up yet?
>
> Rayson
>
> ==
> Open Grid Scheduler - The Official Open Source Grid Engine
> http://gridscheduler.sourceforge.net/
> http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.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] [puppet][kolla] Multi-node installation

[Steven Dake (stdake)]

Kevin,

Thanks for the suggestion.  I'll try what you suggest instead.  We do welcome 
Operators on the openstack-kolla IRC channel; please come join in and help us 
hone our message (and code of course) to match what Operators wan to hear and 
see and is consistent in both cases.  The Kolla community currently provides 
past day-zero deployment operational management toolset for OpenStack.

 I just want to get the message across loud and clear that Kolla is not 
opinionated but provides an out of the box installation experience that 
requires no OpenStack configuration and minimal configuration otherwise.

Regards
-steve

From: "Fox, Kevin M" >
Date: Wednesday, April 13, 2016 at 5:45 AM
To: Steven Dake >, Rayson Ho 
>, Emilien Macchi 
>
Cc: 
"openstack-operators@lists.openstack.org"
 
>
Subject: RE: [Openstack-operators] [puppet][kolla] Multi-node installation

Kolla folks, the word opinionated in the deploymentbconfig tool is usually seen 
by ops as heavily tieing your hands to the point of being very painful or a 
show stopper. I get that your trying to say that now its "opinionated" for easy 
install but supports being unopinionated, but some ops wont read past the first 
part of the sentence. The reaction to the word opinionated can be that strong. 
Best to just claim unopinionated with an easy install option or something like 
that.

Thanks,
Kevin


From: Steven Dake (stdake)
Sent: Wednesday, April 13, 2016 1:40:16 AM
To: Rayson Ho; Emilien Macchi
Cc: 
openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] [puppet][kolla] Multi-node installation

A suggestion to give Kolla a spin inside…

From: Rayson Ho >
Date: Tuesday, April 12, 2016 at 1:58 PM
To: Emilien Macchi >
Cc: 
"openstack-operators@lists.openstack.org"
 
>
Subject: Re: [Openstack-operators] [puppet] Multi-node installation

On Tue, Apr 12, 2016 at 4:17 PM, Emilien Macchi 
> wrote:
> If you need to start a composition layer from scratch, you'll need to
> compose the manifests yourself.
> Puppet OpenStack is not an opinionated project like TripleO, Fuel,
> Kolla. We're a library of Puppet modules that you can use at wish.
> You need to be a bit familiar with Puppet.
> But if you look at wat we do in puppet-openstack-integration, you're
> missing a few parameters to make it work in multi-node, it should not
> be hard.

Thanks for the the prompt reply, Emilien! (And hello from Toronto!)

I am just trying to install OpenStack on a cluster of 3 CentOS machines. I 
tried the OpenStack Ansible installation, but there are 2 showstoppers:
 - OpenStack Ansible works great on Ubuntu, but doesn't support RHEL (we have 
RHEL licenses, we use CentOS and Oracle Linux for R & D. Our production 
machines will be running RHEL so Ubuntu doesn't cut it.)

Rayson,

Kolla deploys multinode with high availability.  Kolla is an opinionated 
deployment management tool unless the Operator has opinions of their own.  
Kolla offers complete customization of any OpenStack parameter via augmentation 
files which override the defaults specified by Kolla.  This permits an Operator 
to have something working right out o the box, but change things around as the 
Operator's experience grows with OpenStack.  Its essentially the best of both 
worlds :)


 - If we install OpenStack behind an HTTP Proxy & firewall, then some parts of 
OpenStack setup do not work well with the proxy. So we install OpenStack 
outside the firewall and then bring them into the datacenter. However, with the 
OpenStack Ansible setup, every time the nodes boot up, they try to contact the 
package servers again to check for newer versions, and thus they would get 
errors as they need to go through the proxy.

Kolla will work well for what I think you desire.  To upgrade kolla, you run 
"kolla-ansible upgrade".  There is no runtime automatic checking for new stuff. 
 Oracle also ships Kolla 1.0.0 as part of their OpenStack implementation.



I use Puppet OpenStack because it works well on RHEL-based OSes & the 
installation doesn't seem to contact the outside world once it is configured. 
And I used Puppet a few years ago (mainly for basic provisioning in AWS/EC2), 
so that's another plus for Puppet. A few weeks ago I looked at Packstack, which 
calls the Puppet installation internally, but last time I used it I 

[Openstack-operators] Community App Catalog IRC meeting Thursday April 14th

[Christopher Aedo]

Join us Thursday for our weekly meeting, scheduled for April 14th at
17:00UTC in #openstack-meeting-3

The agenda can be found here, and please add to if you want to get
something on the agenda:
https://wiki.openstack.org/wiki/Meetings/app-catalog

One topic that might be of interest if you are not a regular attendee
will be our summit plans.  Since the Community App Catalog (which is
not Murano - different things!) crosses over into many different
spaces in OpenStack we would love to get more conversations going with
different projects and working groups.  ESPECIALLY around the subject
of developing applications for OpenStack.  Join us if you can!

Looking forward to seeing everyone there tomorrow!

-Christopher

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

[Openstack-operators] BoF OVN call for ideas/discussion points

[David Medberry]

Hi,

There is a Birds of a Feather session on OVN at Austin.
If you've got experience or questions or issues with OVN, you can register
them here:

https://etherpad.openstack.org/p/AUS-BoF-OVN

and participate in the session:
Wednesday, April 27, 1:50pm-2:30pm

https://www.openstack.org/summit/austin-2016/summit-schedule/events/6871?goback=1

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

[Openstack-operators] Ops Summit Call for Lightning Talks!

[Mike Dorman]

The time is upon us again to put together some great lightning talks for the 
Ops summit!  We’ll have a single block of 90 minutes this time, so will have 
time for lots of good content from our community.

Details and sign up on the etherpad:  
https://etherpad.openstack.org/p/AUS-ops-lightning-talks

* Monday 14:50 - 16:20

* Talks should be 5 - 10 minutes, INCLUDING time for a few questions

* Potential topic ideas:
  * Project updates for existing or new project
  * Architecture show-and-tell (these are always popular and really useful for 
people)
  * Talk about a problem or bug you encountered and how you addressed it
  * Tools/utilities you've developed to help your daily life of running a cloud
  * Success stories/anecdotes about working with the larger community

I highly encourage everyone to participate.  This is a great opportunity to 
share about what you’ve been working on recently, as well as get your feet wet 
with presenting if you’ve never done a formal summit talk before.

Check out the etherpad, and sign up!

Thanks,
Mike


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

Re: [Openstack-operators] Allow to investigate instance actions after instance deletion

[Kris G. Lindgren]

This spec/feature has already done on it and is committed:

https://review.openstack.org/#/q/topic:bp/os-instance-actions-read-deleted-instances

It landed in mitaka.

___
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy

From: Dina Belova >
Date: Wednesday, April 13, 2016 at 4:08 AM
To: George Shuklin >
Cc: 
"openstack-operators@lists.openstack.org"
 
>
Subject: Re: [Openstack-operators] Allow to investigate instance actions after 
instance deletion

George,

I really believe this can be processed via Ceilometer events. Events about all 
actions happened to instance are coming to Ceilometer.

Cheers,
Dina

On Wed, Apr 13, 2016 at 12:23 PM, George Shuklin 
> wrote:
I filed a bug (feature request) about ability to see deleted instances action 
list: https://bugs.launchpad.net/nova/+bug/1569779

Any ideas?

I really want to see it like this:

I filed a bug (feature request) about ability to see deleted instances action 
list: https://bugs.launchpad.net/nova/+bug/1569779

Any ideas?

I really want to see it like this:

+---+--+-++
| Action| Request_ID   | Message | 
Start_Time |
+---+--+-++
| create| req-31f61086-ce71-4e0a-9ef5-3d1bdd386043 | -   | 
2015-05-26T12:09:54.00 |
| reboot| req-4632c799-a83e-489c-bb04-5ed4f47705af | -   | 
2015-05-26T14:21:53.00 |
| stop  | req-120635d8-ef53-4237-b95a-7d15f00ab6bf | -   | 
2015-06-01T08:46:03.00 |
| migrate   | req-bdd680b3-06d5-48e6-868b-d3e4dc17796a | -   | 
2015-06-01T08:48:14.00 |
| confirmResize | req-a9af49d4-833e-404e-86ac-7d8907badd9e | -   | 
2015-06-01T08:58:03.00 |
| start | req-5a2f5295-8b63-4cb7-84d9-dad1c6abf053 | -   | 
2015-06-01T08:58:20.00 |
| delete| req----- | -   | 
2016-04-01T00:00:00.00 |
+---+--+-++




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



--

Best regards,

Dina Belova

Software Engineer

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

[Openstack-operators] [ceilometer][gnocchi] ceilometer to gnocchi guide

[gordon chung]

hi folks,

as you know Gnocchi api is different from Ceilometer's v2 metering api 
(for the better). to help describe the differences and possibly help 
with the transition, i've created a few slides[1] to describe how a 
command in Ceilometer can be done similarly in Gnocchi.

to learn how to install / configure Gnocchi, please check the docs[2]. 
the recommended configuration is still postgresql+ceph.

to learn how to configure it with Ceilometer, please check Ceilometer 
docs[3]

personally, i'd recommend starting at 2.0.x[4] or 2.1.x[5] to minimise 
any required migrations. 2.1.x is newly released so apply your own 
stability concerns/requirements as you do. 2.0.3 will probably be 
released soon with a critical performance fix.

[1] http://www.slideshare.net/GordonChung/ceilometer-to-gnocchi
[2] http://docs.openstack.org/developer/gnocchi/install.html
[3] 
http://docs.openstack.org/developer/ceilometer/install/dbreco.html#moving-from-ceilometer-to-gnocchi
[4] 
http://lists.openstack.org/pipermail/openstack-announce/2016-March/001006.html 

[5] 
http://lists.openstack.org/pipermail/openstack-announce/2016-April/001093.html

cheers,

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

Re: [Openstack-operators] [puppet][kolla] Multi-node installation

[Fox, Kevin M]

Kolla folks, the word opinionated in the deploymentbconfig tool is usually seen 
by ops as heavily tieing your hands to the point of being very painful or a 
show stopper. I get that your trying to say that now its "opinionated" for easy 
install but supports being unopinionated, but some ops wont read past the first 
part of the sentence. The reaction to the word opinionated can be that strong. 
Best to just claim unopinionated with an easy install option or something like 
that.

Thanks,
Kevin


From: Steven Dake (stdake)
Sent: Wednesday, April 13, 2016 1:40:16 AM
To: Rayson Ho; Emilien Macchi
Cc: openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators] [puppet][kolla] Multi-node installation

A suggestion to give Kolla a spin inside…

From: Rayson Ho >
Date: Tuesday, April 12, 2016 at 1:58 PM
To: Emilien Macchi >
Cc: 
"openstack-operators@lists.openstack.org"
 
>
Subject: Re: [Openstack-operators] [puppet] Multi-node installation

On Tue, Apr 12, 2016 at 4:17 PM, Emilien Macchi 
> wrote:
> If you need to start a composition layer from scratch, you'll need to
> compose the manifests yourself.
> Puppet OpenStack is not an opinionated project like TripleO, Fuel,
> Kolla. We're a library of Puppet modules that you can use at wish.
> You need to be a bit familiar with Puppet.
> But if you look at wat we do in puppet-openstack-integration, you're
> missing a few parameters to make it work in multi-node, it should not
> be hard.

Thanks for the the prompt reply, Emilien! (And hello from Toronto!)

I am just trying to install OpenStack on a cluster of 3 CentOS machines. I 
tried the OpenStack Ansible installation, but there are 2 showstoppers:
 - OpenStack Ansible works great on Ubuntu, but doesn't support RHEL (we have 
RHEL licenses, we use CentOS and Oracle Linux for R & D. Our production 
machines will be running RHEL so Ubuntu doesn't cut it.)

Rayson,

Kolla deploys multinode with high availability.  Kolla is an opinionated 
deployment management tool unless the Operator has opinions of their own.  
Kolla offers complete customization of any OpenStack parameter via augmentation 
files which override the defaults specified by Kolla.  This permits an Operator 
to have something working right out o the box, but change things around as the 
Operator's experience grows with OpenStack.  Its essentially the best of both 
worlds :)


 - If we install OpenStack behind an HTTP Proxy & firewall, then some parts of 
OpenStack setup do not work well with the proxy. So we install OpenStack 
outside the firewall and then bring them into the datacenter. However, with the 
OpenStack Ansible setup, every time the nodes boot up, they try to contact the 
package servers again to check for newer versions, and thus they would get 
errors as they need to go through the proxy.

Kolla will work well for what I think you desire.  To upgrade kolla, you run 
"kolla-ansible upgrade".  There is no runtime automatic checking for new stuff. 
 Oracle also ships Kolla 1.0.0 as part of their OpenStack implementation.



I use Puppet OpenStack because it works well on RHEL-based OSes & the 
installation doesn't seem to contact the outside world once it is configured. 
And I used Puppet a few years ago (mainly for basic provisioning in AWS/EC2), 
so that's another plus for Puppet. A few weeks ago I looked at Packstack, which 
calls the Puppet installation internally, but last time I used it I encountered 
other issues. However, as it supports multi-node installations, I think I will 
look at how it calls the Puppet manifests.

If there is an easier way to install OpenStack (ideally 14.0, and we would like 
to stay as close to the official OpenStack source as possible) on RHEL, without 
trying to download newer packages once the installation is done, and runs on 
more than 1 machine, please let me know!

I feel Kolla is pretty easy for operators to use and get their heads around.  I 
always ask new Operators to point out their top 3 pain points after eval.  When 
we started the project it was all over the place.  Now there doesn’t seem to be 
much if any pain points pointed out by Operators when operating Kolla.  A 
majority of people find it intuitive, well designed, and easy to operate and 
manage an OpenStack cloud long  term.  I personally think our top problem at 
this point is lack of documentation around operating Kolla long term – which 
will be rectified in May/June after Austin Summit concludes.

Most folks get a deployment going on bare metal in 1-2 hours – sometimes with a 
little help from the kolla irc channel #kolla on freenode.  Our community runs 
24 hours a day – so drop in if you have questions.  

Re: [Openstack-operators] Draft Agenda for AUS Ops@Summit

[Tom Fifield]

All,

just a quick note to say this is now on the official agenda:

https://www.openstack.org/summit/austin-2016/summit-schedule/#event_types=13,14,15


Don't forget to download your summit app - it has caching magic.


Regards,


Tom

On 08/04/16 12:32, Tom Fifield wrote:

OK, we've had moderator confirmation for many sessions, so I'm going to
start putting this on the official agenda and setting up some etherpads :)

Still haven't heard anyone interested in Ceph or Swift.


Monday  Salon E (112)   Salon D (112)   MR406 (98)  MR409 (55)  MR410
(38)MR412 (38)
11:15 - 11:55   Logging: if you could get one thing fixed this cycle,
what would it be?   Liberty upgrades - what worked, what didn't, what
would we do differently next time   Docs: should the Ops Guide have a new
revision?   Large Deployments Team  WG2 WG3
12:05 - 12:45   Taxonomy of FailuresMitaka: Beyond the Release Notes
Roadmap Feedback Request from Ops   Large Deployments Team  Ask
OpenStack   WG3
12:45 - 2:00Lunch
2:00 - 2:40 Deployment methods  Config Options  Future of op meetups
organisationOSOps   Scientific WG   WG6
2:50 - 3:30 Lightning Talks Customer Onboarding best practices
Session 12  OSOps   Scientific WG   Ops Tags Team
3:40 - 4:20 Lightning Talks Inventory ManagementRequests for
Enhancement Process WG 7Logging Ops Tags Team
4:20 - 4:40 Break
4:40 - 5:20 Containers on OpenStack Ceph IntegrationSession 
18  Ops
Recognition - what is it, and where is it going?NFV/Telco   WG12
5:30 - 6:10 Openstack in Containers Swift Ops   Session 21  
Ops
Recognition - what is it, and where is it going?NFV/Telco   WG12
6:00 - 7:30 Marketplace Booth Crawl Happy Hour!!














Tuesday Other Rooms 




11:15 - 11:55   Scientific WG   











Wednesday   Other Rooms Other Rooms Other Rooms 


9:00 - 12:30

Ansible 


1:50 - 2:30 User Committee  Large Deployment Team   
Puppet  

2:40 - 3:20 User Committee  

Puppet  

3:30 - 4:10 





4:30 - 6:00 

Ansible Puppet  








ThursdayOther Rooms Other Rooms Other Rooms 


9:00 - 10:30Ansible 











11:00 - 11:40   

Chef


11:50 - 12:30   Ansible Puppet  Chef


1:30 - 2:10 

Chef
















Friday  Salon E (112)   Salon C (Lunch) Other Rooms 


09:00 - 12:30   Unstructured
Ansible/Puppet  


12:45 - 1:50
Feedback session / Awards   



2:00 - 4:10 Unstructured




4:20 - 4:40 Break   




4:40 - 5:20 Unstructured








On 05/04/16 10:20, Tom Fifield wrote:

Thanks to those who got back to me yesterday about conflicts.

Today's update is a significant re-wrangling, so check it out below.

I've started matching up moderators to slots based on your sign-ups on
the etherpads - check your email :)

The sessions in Red (general sessions) don't have a moderator yet -
please let me know if you want to sign up for them.
https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide

Similarly, if there is something missing you'd like to chat with
others about, we still have some empty slots.


Monday  Salon E (112)   Salon D (112)   MR406 (98)  MR409 (55)  MR410
(38)MR412 (38)
11:15 - 11:55   Logging: if you could get one thing fixed this cycle,
what would it be?   Liberty upgrades - what worked, what didn't, what
would we do differently next time   Docs: should the Ops Guide have a
new revision?   Large Deployments Team  WG2 WG3
12:05 - 12:45   Taxonomy of FailuresMitaka: Beyond the Release
Notes   Roadmap Feedback Request from Ops   Large Deployments Team
WG2 WG3
12:45 - 1:50Lunch
2:00 - 2:40 Deployment methods  Config Options  Future of op meetups
organisationOSOps   Scientific WG   WG6
2:50 - 3:30 Lightning Talks Customer Onboarding best practices
Session 12  OSOps   Scientific WG   Ops Tags Team
3:40 - 4:20 Lightning Talks Inventory 

Re: [Openstack-operators] Allow to investigate instance actions after instance deletion

[Dina Belova]

George,

I really believe this can be processed via Ceilometer events. Events about
all actions happened to instance are coming to Ceilometer.

Cheers,
Dina

On Wed, Apr 13, 2016 at 12:23 PM, George Shuklin 
wrote:

> I filed a bug (feature request) about ability to see deleted instances
> action list: https://bugs.launchpad.net/nova/+bug/1569779
>
> Any ideas?
>
> I really want to see it like this:
>
> I filed a bug (feature request) about ability to see deleted instances
> action list: https://bugs.launchpad.net/nova/+bug/1569779
>
> Any ideas?
>
> I really want to see it like this:
>
>
> +---+--+-++
> | Action| Request_ID   | Message |
> Start_Time |
>
> +---+--+-++
> | create| req-31f61086-ce71-4e0a-9ef5-3d1bdd386043 | -   |
> 2015-05-26T12:09:54.00 |
> | reboot| req-4632c799-a83e-489c-bb04-5ed4f47705af | -   |
> 2015-05-26T14:21:53.00 |
> | stop  | req-120635d8-ef53-4237-b95a-7d15f00ab6bf | -   |
> 2015-06-01T08:46:03.00 |
> | migrate   | req-bdd680b3-06d5-48e6-868b-d3e4dc17796a | -   |
> 2015-06-01T08:48:14.00 |
> | confirmResize | req-a9af49d4-833e-404e-86ac-7d8907badd9e | -   |
> 2015-06-01T08:58:03.00 |
> | start | req-5a2f5295-8b63-4cb7-84d9-dad1c6abf053 | -   |
> 2015-06-01T08:58:20.00 |
> | delete| req----- | -   |
> 2016-04-01T00:00:00.00 |
>
> +---+--+-++
>
>
>
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>



-- 

Best regards,

Dina Belova

Software Engineer

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

Re: [Openstack-operators] [puppet][kolla] Multi-node installation

[Robert Starmer]

+1 for Kolla (and yes, I realize I just suggested Packstack).  It certainly
is much easier to _operate_ once you get it up and running.

On Wed, Apr 13, 2016 at 1:40 AM, Steven Dake (stdake) 
wrote:

> A suggestion to give Kolla a spin inside…
>
> From: Rayson Ho 
> Date: Tuesday, April 12, 2016 at 1:58 PM
> To: Emilien Macchi 
> Cc: "openstack-operators@lists.openstack.org" <
> openstack-operators@lists.openstack.org>
> Subject: Re: [Openstack-operators] [puppet] Multi-node installation
>
> On Tue, Apr 12, 2016 at 4:17 PM, Emilien Macchi 
> wrote:
> > If you need to start a composition layer from scratch, you'll need to
> > compose the manifests yourself.
> > Puppet OpenStack is not an opinionated project like TripleO, Fuel,
> > Kolla. We're a library of Puppet modules that you can use at wish.
> > You need to be a bit familiar with Puppet.
> > But if you look at wat we do in puppet-openstack-integration, you're
> > missing a few parameters to make it work in multi-node, it should not
> > be hard.
>
> Thanks for the the prompt reply, Emilien! (And hello from Toronto!)
>
> I am just trying to install OpenStack on a cluster of 3 CentOS machines. I
> tried the OpenStack Ansible installation, but there are 2 showstoppers:
>  - OpenStack Ansible works great on Ubuntu, but doesn't support RHEL (we
> have RHEL licenses, we use CentOS and Oracle Linux for R & D. Our
> production machines will be running RHEL so Ubuntu doesn't cut it.)
>
>
> Rayson,
>
> Kolla deploys multinode with high availability.  Kolla is an opinionated
> deployment management tool unless the Operator has opinions of their own.
> Kolla offers complete customization of any OpenStack parameter via
> augmentation files which override the defaults specified by Kolla.  This
> permits an Operator to have something working right out o the box, but
> change things around as the Operator's experience grows with OpenStack.
> Its essentially the best of both worlds :)
>
>
>  - If we install OpenStack behind an HTTP Proxy & firewall, then some
> parts of OpenStack setup do not work well with the proxy. So we install
> OpenStack outside the firewall and then bring them into the datacenter.
> However, with the OpenStack Ansible setup, every time the nodes boot up,
> they try to contact the package servers again to check for newer versions,
> and thus they would get errors as they need to go through the proxy.
>
>
> Kolla will work well for what I think you desire.  To upgrade kolla, you
> run "kolla-ansible upgrade".  There is no runtime automatic checking for
> new stuff.  Oracle also ships Kolla 1.0.0 as part of their OpenStack
> implementation.
>
>
>
> I use Puppet OpenStack because it works well on RHEL-based OSes & the
> installation doesn't seem to contact the outside world once it is
> configured. And I used Puppet a few years ago (mainly for basic
> provisioning in AWS/EC2), so that's another plus for Puppet. A few weeks
> ago I looked at Packstack, which calls the Puppet installation internally,
> but last time I used it I encountered other issues. However, as it supports
> multi-node installations, I think I will look at how it calls the Puppet
> manifests.
>
> If there is an easier way to install OpenStack (ideally 14.0, and we would
> like to stay as close to the official OpenStack source as possible) on
> RHEL, without trying to download newer packages once the installation is
> done, and runs on more than 1 machine, please let me know!
>
>
> I feel Kolla is pretty easy for operators to use and get their heads
> around.  I always ask new Operators to point out their top 3 pain points
> after eval.  When we started the project it was all over the place.  Now
> there doesn’t seem to be much if any pain points pointed out by Operators
> when operating Kolla.  A majority of people find it intuitive, well
> designed, and easy to operate and manage an OpenStack cloud long  term.  I
> personally think our top problem at this point is lack of documentation
> around operating Kolla long term – which will be rectified in May/June
> after Austin Summit concludes.
>
> Most folks get a deployment going on bare metal in 1-2 hours – sometimes
> with a little help from the kolla irc channel #kolla on freenode.  Our
> community runs 24 hours a day – so drop in if you have questions.  OSAD and
> Kolla are completely different experiences – the only thing they really
> have in common is the usage of Ansible as a dependency.
>
> Kolla documentation is here:
> http://docs.openstack.org/developer/kolla
>
> The Kolla repository is here:
> http://github.com/openstack/kolla
>
> To find out more about the design check out this Ansible blog post:
> https://www.ansible.com/blog/openstack-kolla
>
> In the recent user survey published, 1% of respondents are using Kolla in
> production, and 3% are using in testing.  This is up from zero in the last
> survey ;)  (Kolla entered the big tent 10 

[Openstack-operators] Allow to investigate instance actions after instance deletion

[George Shuklin]

I filed a bug (feature request) about ability to see deleted instances 
action list: https://bugs.launchpad.net/nova/+bug/1569779


Any ideas?

I really want to see it like this:

I filed a bug (feature request) about ability to see deleted instances 
action list: https://bugs.launchpad.net/nova/+bug/1569779


Any ideas?

I really want to see it like this:

+---+--+-++
| Action| Request_ID   | Message | 
Start_Time |
+---+--+-++
| create| req-31f61086-ce71-4e0a-9ef5-3d1bdd386043 | -   | 
2015-05-26T12:09:54.00 |
| reboot| req-4632c799-a83e-489c-bb04-5ed4f47705af | -   | 
2015-05-26T14:21:53.00 |
| stop  | req-120635d8-ef53-4237-b95a-7d15f00ab6bf | -   | 
2015-06-01T08:46:03.00 |
| migrate   | req-bdd680b3-06d5-48e6-868b-d3e4dc17796a | -   | 
2015-06-01T08:48:14.00 |
| confirmResize | req-a9af49d4-833e-404e-86ac-7d8907badd9e | -   | 
2015-06-01T08:58:03.00 |
| start | req-5a2f5295-8b63-4cb7-84d9-dad1c6abf053 | -   | 
2015-06-01T08:58:20.00 |
| delete| req----- | -   | 
2016-04-01T00:00:00.00 |
+---+--+-++




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