Another question is what type of SSD's are you using. There is a big
difference between not just vendors of SSD's but the size of them as their
internals make a big difference on how the OS interacts with them.
This link is still very usage today:
I believe you can actually do this in Liberty..
http://docs.openstack.org/liberty/networking-guide/adv-config-network-rbac.html
On Mon, Oct 3, 2016 at 1:00 AM, Kevin Benton wrote:
> You will need mitaka to get an external network that is only available to
> specific
I think many people tried to run ceilometer with multiple different
backends and for a while were truly unsuccessful.
If you look at Liberty and now in Mitaka there has been a lot of work to
separate out the alarms from the actual data parts. You now have Adoh from
the alarming standpoint, and
It has been merged.
On Thu, Sep 15, 2016 at 9:44 AM, Tong Li wrote:
> Dear openstack/osop-tools-contrib core reviewers, please review the
> following patch which provides ansible and terraform work load tests for
> Interop-challenge effort.
>
>
I'm not sure if this fits what you need, but the Kolla project produces a
lot of default values that are included in their deployments. You could
check that out and see if it works for you.
On Wed, Sep 7, 2016 at 6:51 PM, Graeme Gillies wrote:
> On 08/09/16 05:41, Dan
hey are looking at doing hybrid cloud. Or they may want to ensure
> that two of their own private clouds are interop compatible.
>
>
>
> ___
>
> Kris Lindgren
>
> Senior Linux Systems Engineer
>
> GoDa
ou indicated,
> that would be a good place for us to ask questions. Thanks!
>
> Catherine Diep
> RefStack Project PTL
> IBM
> - Forwarded by Catherine Cuong Diep/San Jose/IBM on 08/31/2016 01:25
> PM -----
>
> From: "Kris G. Lindgren" <klindg...@godaddy.
HI there,
That patch was merged earlier today..
The patch was rebased at 2pm EST. IT was reviewed earlier this morning
again, and then +1 on the 25th of August.
You should be good to go. If you do have any questions like this the
OSOps Working Group is out there to help as well. We had
got a +2
> > on it at least.
> +1
>
> I had contacted JJ earlier and he told me that the best person to contact
> would be Joseph Bajin (RaginBajin in IRC). I've also added an OSOps tag to
> this message.
> >
> > -Christopher
> >
> >> On Tue, Aug
We let our people access the Glance API. Glance uses Keystone, so user
authentication is done the same way all the other services are done within
OpenStack. We allow the glance api ports to be available to them so they
can use the service.
What are you thinking that would prevent you from
Hello,
I'm going to have to cancel this week's OSOps meeting set for this today,
unless someone volunteers to run the meeting.
If not, then the next meeting is set for August 3rd, 2016 with the same
agenda.
--Joe
On Mon, Jul 18, 2016 at 7:41 PM, Joseph Bajin <josephba...@gmail.com>
Everyone,
The agenda is up for this week's OSOps meeting. You can find the agenda
here:
https://etherpad.openstack.org/p/osops-irc-meeting-20160720
I hope to have some ideas on how OSOps can help and how we can get more
people to participate.
The meeting will start at 1900 UTC in
Hi there,
It looks like QOS is already available within the Mitaka release. Maybe
it doesn't have all the features you need, but looks to be a good start.
http://docs.openstack.org/mitaka/networking-guide/adv-config-qos.html
I haven't used it yet, but maybe someone else will pipe up with some
, 2016 at 8:44 AM, Joseph Bajin <josephba...@gmail.com> wrote:
> Operators,
>
> Our bi-weekly meeting is today in the #openstack-meeting-4 room beginning
> at 1900 UTC.
>
> There isn't much on the agenda today, as we haven't gotten a lot of
> participation or vol
Operators,
Our bi-weekly meeting is today in the #openstack-meeting-4 room beginning
at 1900 UTC.
There isn't much on the agenda today, as we haven't gotten a lot of
participation or volunteering. You can review the agenda here. [1] If
you have anything that you think the Operators community
All the different projects have different ways of reporting bugs and
looking for features.
You can see a few of the different ways that the Operators discussed back
at the Summit here -
https://etherpad.openstack.org/p/AUS-ops-Requests-for-Enhancement-Process
That should give you some more
Everyone,
Our next OSops group meeting will be help this coming Wednesday at 1900 UTC
in the #openstack-meeting-4 IRC room.
I've posted our agenda for this week:
https://etherpad.openstack.org/p/osops-irc-meeting-20160518
Thanks
Joe
___
Everyone,
The OSOps team would like to get help from the Operator Community to help
gather issues and problems from the informal Operators meetup.[1]
Here is the etherpad that we have setup.[2] We are asking users to take a
look at the etherpad[1] and if they identify issues that should be
There is also a golang library that can validate tokens..
http://gophercloud.io/docs/identity/v3/
On Thu, May 12, 2016 at 11:25 PM, David Medberry
wrote:
> There's a jython implementation of keystone and I thought there was other
> work to validate tokens from within
On Thu, May 12, 2016 at 5:04 PM, Joshua Harlow
wrote:
> Hi there all-ye-operators,
>
> I am investigating how to help move godaddy from rpms to a container-like
> solution (virtualenvs, lxc, or docker...) and a set of questions that comes
> up is the following (and I would
Operators,
The Nova team has requested feedback from the community and especially the
operators on two specs that they are reviewing.
The first spec is regarding some logging changes to the scheduler:
- Mailing List:
http://lists.openstack.org/pipermail/openstack-operators/2016-May/010322.html
Everyone,
The OSOps group will be having their next meeting tomorrow May 4th, 2016 at
1900 UTC.
It will be hosted in the #openstack-meeting-4 room.
The agenda has been added to the etherpad and wiki. You can find that
here. [1] The primary goal is to follow-up on the discussions that we had
at
Hello Operators,
I wanted to provide some updates to the OSOps Operators Meeting that was
held last week.
You can find the etherpad located here. [1]
The highlights of the meeting were the following:
- People see OSOps as an advocation group for patches, tools, and features
that operators need
Hello Operators,
I wanted to provide some updates to the Requests for Enhancement Process
Operators Meeting that was held last week.
You can find the etherpad located here. [1]
The highlights of the meeting were the following:
- RFE's should be groomed by the Operators first before being sent
tools and their tool
> repository.
>
> Tim
>
> From: Joseph Bajin <josephba...@gmail.com>
> Date: Friday 22 April 2016 at 17:55
> To: Robert Starmer <rob...@kumul.us>
> Cc: openstack-operators <openstack-operators@lists.openstack.org>
> Subject: Re: [Openstack-op
Rob/Jay,
The use of the OSOps Working group and its repos is a great way to address
this.. If any of you are coming to the Summit, please take a look at our
Etherpad that we have created.[1] This could be a great discussion topic
for the working sessions and we can brainstorm how we could help
Operators,
The OSOPs Summit etherpad is up and running. You can find this etherpad
located here. [1]
For those that are not aware of OSOps, it stands for OpenStack Operators.
Currently, we maintain the operators focused github repositories as well as
working with other projects to help address
OSOps,
I'm thinking it may be good to cancel this week's OSOps meeting and just
meet during the summit. We have 3 sessions that surround the topics that
we have been talking about and I hope we can get some more topics as well
as participation next week.
Here are the details for the sessions at
Hi Carl,
This is great..
We also have two sessions going on for Operators in hopes to determine the
best methods for gathering these types of requirements. This is to help
Operators get them to the right people as well as ways for the Operators to
track these for follow-up. The two sessions
t;
> [1]https://wiki.openstack.org/wiki/ProductTeam
> [2]https://github.com/openstack/openstack-user-stories
> [3]http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg
>
> On Tue, Apr 5, 2016 at 12:29 PM, Joseph Bajin <josephba...@gmail.com>
> wrote:
>
>> Hi
we (me) are keen
> to engage and help,
>
> Let us know if anyone else is on the same level working on things,
>
> c
>
>
> Christoph Andreas Torlinski
>
> +44(0)7872413856 UK Mobile
>
> christ...@nuagenetworks.net
>
> On 26 March 2016 at 20:47, Joseph Bajin &
Just sending this out to the Operator Community for more feedback.
We'll be having a session at the summit about it, but I'd like to get this
discussion going a little more here if we could.
--Joe
On Sat, Mar 26, 2016 at 4:47 PM, Joseph Bajin <josephba...@gmail.com> wrote:
>
We use the host-route flag as mentioned above. It makes it easy to sent
internet like traffic to a gateway type of box and internal traffic to the
inside for tenants that do have public access.
On Sat, Apr 2, 2016 at 10:33 PM, James Denton
wrote:
> Hi Mike,
>
> You
While I think it's fine to remove this from the normal setup, I think there
should be either a file or process that one could run to add these basic
flavors. I think without you will have things such as DevStack and other
beginners not being able to get up and going.
I think having the migration
Operators,
At the last OSOps Tools and Monitoring meeting, we had mriedem (Nova Team)
talk with us about a proposal that they are working on. The Nova team would
like to abandon the use of a wish-list as it has grown to an unmanageable
size. They have posted a few times to both the operators
Operators,
We will be having our bi-weekly meeting in the #openstack-meeting-4 room at
1900UTC.
I have published the current agenda for this meeting. You can find that
here:
https://etherpad.openstack.org/p/osops-irc-meeting-20160323
Either let me know or please go ahead and add to the ether
Operators,
The Operators Tools and Monitoring Working Group met at its new time 1900
UTC today.
Meeting notes can be found here:
* https://etherpad.openstack.org/p/ops-tools-monitoring-agenda-20150923
We also have a wiki page that we are updating which can be found here:
*
We recently just upgraded to Juno from Icehouse.
We used the upgrade_levels feature to get Nova off the ground, but ran into
major issues around conductor being too slow to respond to messages and
would cause a lot of our instances to not create. This would only happen
at a particular high
Hi Everyone,
One of the items taken from the Operators Meet-up was that the time (10am
EST) was too early for the west coast people. I've been looking at the
meeting calendar and have a few suggested times that I'd like to see if
they would work for others to get more participation.
Odd every
I agree with all of these items especially with not having Vendor booths.
The only thing I would want to mention is that it would be great to have
something centrally located within the US, if we are going to choose the US
for a session. That way it is only a 3-4 hour flight instead of a 7-9
I think those from the Infra Project are a great start, but I do think they
are missing a lot.
Instead of breaking down the message into parts, it just breaks down the
type (INFO, DEBUG, etc) and then makes the rest of the message greedy.
That doesn't help searching or graphing or anything like
Hi,
We didn't have a lot of people attend this session (most likely because it
was schedule at 5:30 so many probably went off to dinner), but those that
did attend provided great input.
Coverage of the session can be found at this etherpad:
Hi,
I wanted to provide a recap of the CMDB working group from the Summit.
There was good attendance with people that had a great amount of experience
working and building a CMDB. While it may seem easy on the surface, it
actually is a pretty big project with a lot of different options and
Hi,
I will be moderating the Customer On-Boarding/Off-Boarding[1] session at
the summit, and wanted to make sure we get as much feedback into the
etherpad[2] as possible.
Both adding and removing users seems like a pretty simple idea, but it gets
complicated pretty quickly. So any suggestions,
Just to add in my $0.02, we run in multiple sites as well. We are using
regions to do this. Cells at this point have a lot going for it, but we
thought it wasn't there yet. We also don't have the necessary resources to
make our own changes to it like a few other places do.
With that, we said
The Policy file is not a filtering agent. It basically just provides ACL
type of abilities.
Can you do this action? True/False
Do you have the right permissions to call this action? True/False
If you wanted to pull back just the instances that the user owns, then you
would actually have to
I wanted to see about getting some Operator Help to push through a
patch[1].
The patch is to not give the user a 404 message back when they click the
cancel button why trying to change their password or the user settings. The
patch resets the page.
It's been sitting there for a while, but
The size of MTU only really matters for the server and client. The
between connections need to be larger than the packets that are being sent.
Scenario 1:
Server - 1400 MTU
Client - 1400 MTU
Switches - 9216 MTU
OVS - 1500 MTU
Result: Successful - Traffic passes without any issue
Scenario 2:
You do have to create something for cinder to have as a backend. That
could be an LVM volume on a particular node, or it could be a CEPH setup,
that's up to your requirements.
Also, you didn't state the error that you are getting when you try to
create a cinder volume. That would certainly help
49 matches
Mail list logo