Hi,
Could everyone please test OpenStack+SELinux with the latest RHEL7.0 builds.
We are running into the same avc's that have fixes released for them.
https://brewweb.devel.redhat.com/buildinfo?buildID=357647
Thank you.
Regards,
Miroslav and Ryan
_
Currently, when you delete a tenant that has 1 or more running instances, the
tenant will be deleted
without warning and the running instance(s) will be left in place. Should there
be a warning
and should the admin be allowed to do this? Or should it be left be?
Thanks,
-Ryan Hallisey
.CONF
transport = messaging.get_transport(CONF)
notifier = messaging.Notifier(transport,
'test_pub_id',
driver='messaging',
topic='notifications')
notifier.info({}, "som
#x27;.info' suffix to the topic that you provided?
I think you should use topic=' notification.info '.
Thanks,
Nader.
On Mon, Apr 14, 2014 at 12:02 PM, Ryan Hallisey < rhall...@redhat.com > wrote:
Hello,
I am unable to send a keystone notification with these parameters in
, mysql, and rabbitmq.
Feel free to take ownership of a service!
Thanks,
Ryan Hallisey
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Great work Daneyon! Excellent job with neutron and nova-networking!
+1
-Ryan
- Original Message -
From: "Steven Dake"
To: "OpenStack Development Mailing List"
Sent: Wednesday, October 22, 2014 11:04:24 AM
Subject: [openstack-dev] [kolla] making Daneyon Hansen core
A few weeks ago in I
Hi,
You can handle this one of two ways.
1)
semanage port -m -t -p tcp 5000
Which will relabel port 5000 as whatever you choose.
2)
Or you could allow to bind to commplex_main_port_t
allow commplex_main_port_t:tcp_socket name_bind;
This will allow to connect to any port labeled
commplex_
+1
I think it's an excellent addition to kolla.
I think this should help tremendously with usability and building better docs
around how to use kolla.
-Ryan
> On Oct 23, 2015, at 5:33 PM, Harm Weites wrote:
>
> +1 this sort of stuff makes live a lot better :)
>
> Swapnil Kulkarni schreef op
+1 Nice work Michal.
-Ryan
- Original Message -
From: "Sam Yaple"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Friday, November 13, 2015 1:15:05 PM
Subject: Re: [openstack-dev] [kolla] Proposing Michal Rostecki for Core
Reviewer (nihilfer on IRC)
Michal do
+1 nice work mlima!
-Ryan
- Original Message -
From: "Vikram Hosakote (vhosakot)"
To: openstack-dev@lists.openstack.org
Sent: Wednesday, May 18, 2016 9:45:53 AM
Subject: Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer
Yes, +1 for sure!
Thanks a lot Mauricio for
Hi all,
At the Kolla meeting last week, I brought up some of the challenges around the
bootstrapping
process in Kubernetes. The main highlight revolved around how the
bootstrapping process will
work.
Currently, in the kolla-kubernetes spec [1], the process for bootstrapping
involves
outside o
Thx,
britt
On 5/22/16, 3:50 PM, "Ryan Hallisey" wrote:
>Hi all,
>
>At the Kolla meeting last week, I brought up some of the challenges around the
>bootstrapping
>process in Kubernetes. The main highlight revolved around how the
>bootstrapping process will
>
st that. Hiding it in an init container makes that much harder for Operators.
As an Op, we need the ability to tweak the workflow as needed and run/rerun
only the pieces that we need.
Thanks,
Kevin
____
From: Ryan Hallisey [rhall...@redhat.com]
Sent: Sunday,
he automagic that is happening. As an Op, I'd
rather it be explicit, out front, where I know its happening, and I can easily
tweak the workflow when necessary to get out of a bind.
Thanks,
Kevin
____
From: Ryan Hallisey [rhall...@redhat.com]
Sent: Thursday, May
Hi all,
When orchestrating an openstack service from nothing, there are a few steps that
need to occur before you have a running service assuming the database already
exists.
- Create the service's users and add a password into the databse
- Sync the service with the database
- Start
Looking at some of the capabilities jinja2 has, it's hard to justify changing
the method already in place.
I think jinja2 can provide a clear and operational way for operators to
customize the dockerfiles as needed.
Kolla just hasn't applied them yet.
I'm extremely hesitant to agree on changing
Thanks for all the hard work Jeff! I'm sure our paths will cross again!
-Ryan
- Original Message -
From: "Michał Jastrzębski"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, June 6, 2016 7:13:00 PM
Subject: Re: [openstack-dev] [kolla] stepping down fro
+1
> On Jun 8, 2016, at 11:43 PM, Vikram Hosakote (vhosakot)
> wrote:
>
> +1
>
> Regards,
> Vikram Hosakote
> IRC: vhosakot
>
> From: "Swapnil Kulkarni (coolsvap)"
> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: Wednesday, June 8, 2016 at 8:54 AM
> To:
Sergey,
Thanks for reaching out to the community! I think there is a lot to discuss. I
added some comments on
the spec and I'm sure many kolla folks will follow up.
Thanks,
Ryan
- Original Message -
From: "Sergey Lukjanov"
To: "OpenStack Development Mailing List"
Sent: Thursday, Jun
Hey Carlos,
The work to enable you to do this is in progress. Kolla needs to refactor the
way the Dockerfiles
are templated in order to create additional flexibility.
You can follow the work here:
https://blueprints.launchpad.net/kolla/+spec/third-party-plugin-support
Thanks,
Ryan
- Orig
Hey Jeff,
Can you write up a spec with the details? That way the community can see the
full layout
of the proposal.
Thanks,
-Ryan
- Original Message -
From: "Jeffrey Zhang"
To: "OpenStack Development Mailing List"
Sent: Wednesday, June 29, 2016 8:50:28 AM
Subject: [openstack-dev] [ko
Angus and Michal,
Thanks for your hard work! I hope our paths will cross again in the future.
Good luck!
Ryan
- Original Message -
From: "Martin André"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Friday, July 8, 2016 7:34:27 AM
Subject: Re: [openstack-dev]
+1
- Original Message -
From: "Paul Bourke"
To: openstack-dev@lists.openstack.org
Sent: Tuesday, March 29, 2016 12:10:38 PM
Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core
Reviewer
+1
On 29/03/16 17:07, Steven Dake (stdake) wrote:
> Hey folks,
>
> Consider
Agreed this needs to happen +1,
- Original Message -
From: "Jeff Peeler"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Wednesday, March 30, 2016 1:22:31 PM
Subject: Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty
within the Liberty branch
O
Good idea Emilien!
Working in both tripleo and Kolla, I'd like to be a part of the conversation.
-Ryan
- Original Message -
From: "Samuel Cassiba"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Thursday, March 31, 2016 6:08:28 PM
Subject: Re: [openstack-dev]
I'm definitely guilty of nit picking docs. I'm fine with holding back and
following up with a patch to fix any grammar/misspelling mistakes. +1
-Ryan
- Original Message -
From: "Paul Bourke"
To: openstack-dev@lists.openstack.org
Sent: Tuesday, April 12, 2016 4:49:09 AM
Subject: Re: [
Just want to give everyone a heads up about a schedule change for kolla
summit sessions. Kolla-kubernetes was a kolla spec [1] that we had intended
to cover at summit in a design session. We are going to change it to a fish
bowl
session instead to be held on Wednesday at 9am and the documentatio
+1
- Original Message -
From: "Angus Salkeld"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Sunday, April 24, 2016 11:01:38 AM
Subject: Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic
+1
On Sat, 23 Apr 2016 3:08 am Michał Rostecki <
-1 to not having a separate kolla-kubernetes repo.
> The kubernetes codebase will be maintained in the
> https://github.com/openstack/kolla repository under the kubernees top level
> directory.
I don't agree here. This needs to be its own repo.
> I feel we made a couple errors with the creati
hey want to
work on an offshoot repository and open us up to the possible problems above.
If you are on this list:
* Ryan Hallisey
* Britt Houser
* mark casey
* Steven Dake (delta-alpha-kilo-echo)
* Michael Schmidt
* Marian Schwarz
* Andrew Batty
>I am in the favor of having two separate repos and evaluating the
>merge/split option later.
>Though in the longer run, I would recommend having a single repo with
>multiple stable deployment tools(maybe too early to comment views but
>yeah)
>
>Swapnil
>Swapnil,
>I gather this is what people wan
+1 to start kolla-kubernetes work.
- Original Message -
From: "Swapnil Kulkarni"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, May 2, 2016 12:59:40 AM
Subject: Re: [openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes
repository management
e
>> Packaging without ansible is simpler as the ansible directory need not
>>be
>> deleted
>>
>> There were other complaints but not many pros. Unfortunately I failed
>>to
>> communicate these complaints to the core team prior to the vote, so now
Hello all,
Harm, really appreciate all your reviews. You were always very thorough and
insightful. You'll always be welcome back to the core team in the future.
Thanks for everything Harm!
+1
-Ryan
- Original Message -
From: "Michal Rostecki"
To: openstack-dev@lists.openstack.org
S
Hello,
I think creating a separate kolla-mesos meeting is a good idea. My only issue
is that I'm a little afraid it might separate our community a little, but I
think it's necessary for kolla-mesos to grow. My other thought is what is
there to come of other kolla-* repos? That being not only k
+1 nice work!
-Ryan
- Original Message -
From: "Steven Dake (stdake)"
To: openstack-dev@lists.openstack.org
Sent: Tuesday, January 19, 2016 3:26:38 AM
Subject: [openstack-dev] [kolla] Nominating Lei Zhang (Jeffrey Zhang in
English) - jeffrey4l on irc
Hi folks,
I would like to propose
+1 I echo all the prior comments.
-Ryan
- Original Message -
From: "Steven Dake (stdake)"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, July 13, 2015 10:40:11 PM
Subject: [openstack-dev] [kolla] Proposal for Paul Bourke for Kolla Core
Hey folks,
I
Tagging kolla so the kolla community also sees it.
Pardon the top posting.
-Ryan
- Original Message -
From: "Dan Prince"
To: "openstack-dev"
Sent: Wednesday, August 5, 2015 2:29:13 PM
Subject: [openstack-dev] [TripleO] [Puppet] Deploying OpenStack with Puppet
modules on Docker with Hea
- Original Message -
From: "James Slagle"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Friday, August 7, 2015 11:20:59 AM
Subject: Re: [openstack-dev] [kolla][tripleo] Deprecating config-internal
On Fri, Aug 7, 2015 at 11:08 AM, Dan Prince wrote:
> On Fri,
> I have a few questions:
> * when do you run puppet? before starting the container so we can
> generate a configuration file?
We would run puppet before starting the container that way puppet can
generate the config and the container absorb it.
> * so iiuc, Puppet is only here to generate Open
+1 Nice job!
-Ryan
- Original Message -
From: "Steven Dake (stdake)"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Friday, August 14, 2015 9:29:10 AM
Subject: [openstack-dev] [kolla] Proposing Swapnil Kulkarni (coolsvap) for
kolla core reviewer team
Hi folk
> Core reviewers:
> Please vote +1 if you ARE satisfied with integration with third party
> unusable without a license software, specifically Cinder volume drivers,
> Neutron network drivers, and various for-pay distributions of OpenStack and
> container runtimes.
> Please vote –1 if you ARE N
Way to go Michal! +1
-Ryan
- Original Message -
From: "Swapnil Kulkarni"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Wednesday, September 30, 2015 5:00:27 AM
Subject: Re: [openstack-dev] [kolla] proposing Michal Jastrzebski (inc0) for
core reviewer
On W
+1
Sam has done an great job integrating his work into Kolla and I look forward to
seeing more of his contributions!
-Ryan
- Original Message -
From: "Andre Martin"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, May 25, 2015 9:37:24 PM
Subject: Re: [
After some upstream discussion, moving the meeting from 1600 to 1700 UTC does
not seem very popular.
It was brought up that changing the time to 16:30 UTC could accommodate more
people.
For the people that attend the 1600 UTC meeting time slot can you post further
feedback to address this?
Tha
+1 Great job with Cinder.
-Ryan
- Original Message -
From: "Steven Dake (stdake)"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Sunday, June 14, 2015 1:48:48 PM
Subject: [openstack-dev] [kolla] Proposal for new core-reviewer Harm Waites
Hey folks,
I am pro
+1. Nice work Angus!
-Ryan
> On Feb 19, 2016, at 11:51 PM, Michał Jastrzębski wrote:
>
> +1 on condition that he will appear in kolla itself, after
> all...you'll be a kolla core as well right?;)
>
>> On 19 February 2016 at 21:44, Sam Yaple wrote:
>> +1 of course. I mean, its Angus. Who can
Hi all.
I'm a little conflicted with my vote. I'm against the concept of backporting a
feature, but
this feature also has some important additions to stability. It's just whether
or not the
stability advantages are critical enough. To me, it seems like they are.
I just want to note that we ne
Hey Steve,
I think the concept of having a limit on cores from a company or a block on #
core reviewers
from the same company on a patch is not the right approach. I understand the
methodology behind
this is to make sure we stay honest to the code base and objective when
reviewing, but I don't
Hello,
I have experience writing selinux policy. My plan was to write the selinux
policy for Kolla in the next cycle. I'd be interested in joining if that fits
the criteria here.
Thanks,
-Ryan
- Original Message -
From: "Steven Dake (stdake)"
To: "OpenStack Development Mailing List (
+1 Nice Job Alicja!
-Ryan
- Original Message -
From: "Eric LEMOINE"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Friday, March 4, 2016 5:04:10 PM
Subject: Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for
core reviewer
+1
Looking forwa
Another tricky situation..
Given that changes to Docker were the cause of the first two backports I'd
consider those to not be exceptions, but necessary adaptations that Kolla has
to deal with. Unfortunately, this case seems more like an exception. But, I'm
not opposed to a necessary exceptio
*Snip*
> Indeed, this has literally none of the benefits of the ideal Heat
> deployment enumerated above save one: it may be entirely the wrong tool
> in every way for the job it's being asked to do, but at least it is
> still well-integrated with the rest of the infrastructure.
> Now, at the
>>> Hello,
>>>
>>> So Ryan, I think you can make use of heat all the way. Architecture of
>>> kolla doesn't require you to use ansible at all (in fact, we separate
>>> ansible code to a different repo). Truth is that ansible-kolla is
>>> developed by most people and considered "the way to deploy ko
+1 for sure
-Ryan
- Original Message -
From: "Paul Bourke"
To: openstack-dev@lists.openstack.org
Sent: Friday, March 25, 2016 11:43:06 AM
Subject: Re: [openstack-dev] [kolla][vote] deprecation of icehosue/juno/kilo
branches
+1
On 25/03/16 15:36, Steven Dake (stdake) wrote:
> Hey folks
tracked in the repo I linked above.
Thanks,
Ryan Hallisey
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/
> I think this at some point might be single biggest benefit of using
> helm on the long run - leverage infrastructure charts that aren't
> openstack-centric. Things like etcd are already written and
> potentially we can just help support them.
I think the tools that are being discussion here are
koala bear
-Ryan
- Original Message -
From: "Vikram Hosakote (vhosakot)"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Saturday, July 16, 2016 1:24:08 PM
Subject: Re: [openstack-dev] [kolla] our mascot - input needed
Sorry, I missed the kolla mid-cycle summi
+1
-Ryan
- Original Message -
From: "Jeffrey Zhang"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, July 18, 2016 9:16:09 PM
Subject: Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag
+1 to apply
I'd like to be the volunteer.
On Mon, J
Hello.
The repo split discussion that started at summit was brought up again at the
midcycle.
The discussion was focused around splitting the Docker containers and Ansible
code into
two separate repos [1].
One of the main opponents to the split is backports. Backports will need to be
done
by
ut Newton
>which is only 1 month ahead.
>
>I'm +1 on splitting ansible deployment code into kolla-ansible.
>
>Martin
>
>> Regards
>> -steve
>>
>>
>> On 7/20/16, 1:48 PM, "Ryan Hallisey" wrote:
>>
>>>Hello.
>>>
&
Hi all,
The kolla-kubernetes project is in need of introducing some changes into
kolla's globals.yml. This could quickly become an issue because the community
does not want to have too many variables exposed and create a mess for any
backports.
In order to get kolla-kubernetes unblocked, kolla-k
Hi,
There are a few additional items needed here before you can use the container
work
from tht in the undercloud.
First, we deploy on Atomic. Atomic already has docker started when it boots.
We can't
use Atomic for the undercloud because there is no yum to install the clients.
The clients
w
+1
-Ryan
- Original Message -
From: "Steven Dake (stdake)"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Thursday, August 18, 2016 7:09:35 PM
Subject: [openstack-dev] [vote][kolla] Core nomination proposal for Eduardo
Gonzalez Gutierrez (egonzales90 on irc)
+1
-Ryan
- Original Message -
From: "Michał Jastrzębski"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Wednesday, August 24, 2016 10:41:57 AM
Subject: Re: [openstack-dev] [kolla][vote] Core nomination for Dave Walker
(Daviey on irc)
+1 good job Davey:)
On
Option c.
- Ryan
> On Sep 15, 2016, at 4:33 AM, Paul Bourke wrote:
>
> c) Split the repository shortly after tagging 3.0.0 – creating a
> kolla-ansible deliverable for Ocata.
>
>> On 15/09/16 07:12, Steven Dake (stdake) wrote:
>> Core Reviewers:
>>
>>
>>
>> The facts:
>>
>> We have
option 2
Thanks
-Ryan
- Original Message -
From: "Mauricio Lima"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, September 19, 2016 2:21:51 PM
Subject: Re: [openstack-dev] [vote][kolla] deprecation for fedora distro
support
Option 2
2016-09-1
I agree with Michal and Martin. I was a little reluctant to respond here
because the Debian additions are new, while Fedora has been around since the
beginning and never got a ton of testing.
Berendt what's your take here?
Thanks,
Ryan
- Original Message -
From: "Michał Jastrzębski"
Thanks for starting the discussion Fabio.
> As someone that started looking into this topic just recently, I'd love to see
> our communities collaborate more wherever possible. For example, it'd be great
> to see us working on a reference architecture for deploying OpenStack on
> kubernetes, letti
Hi all,
There has been a bunch of new contributors looking for the best way
to get into kolla-kubernetes community. I want to guide anyone
interested in joining the community by providing some low hanging
fruit as well as a few suggestions.
***Quickstart***
https://github.com/openstack/koll
Hey folks,
I wanted to highlight some of the discussion that was held at summit
and outline goals for kolla-kubernetes in the Ocata cycle.
The number one goal for the kolla-kubernetes project in the Ocata cycle is to
have a 1.0 release. As discussed at summit, the community is going to pursue
He
+1
-Ryan
- Original Message -
From: "Swapnil Kulkarni"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Friday, November 4, 2016 8:48:49 AM
Subject: Re: [openstack-dev] [kolla] Propose removal of TrivialFix
requirement
On Thu, Nov 3, 2016 at 6:51 PM, Paul
Hey folks,
The kolla-kubernetes architecture spec has been under review
for a day now. The plan is to keep it open for 7 days after
the initial review was posted (November 8th). Therefore, voting on
the spec will commence on November 15th. So be sure to add any input
you may have before that date
Forgot to include the link to the spec :)
https://review.openstack.org/#/c/392257/
Thanks,
Ryan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:u
Hey folks,
There has been a lot of input in the spec and tons IRC discussion
over the last two days. I'm glad the discussion is very active :).
The goal of the spec is to capture the ideas and the discussion in
one readable doc so no one has to read the 1 lines of IRC
discussion that has occ
+1
-Ryan
- Original Message -
From: "Michał Jastrzębski"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Wednesday, November 16, 2016 1:23:27 PM
Subject: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core
election policy change - vote
Hello,
Hey folks,
I spoke with the Kubernetes community manager about the interop
between Openstack and Kubernetes with respect to Kolla. We agreed
that it would make sense to have a channel in the Kubernetes Slack
group for kolla.
In addition, we talked about mirroring the slack and irc channels
essen
The topic wasn't very clear. Fixing that...
-Ryan
- Original Message -
From: "Ryan Hallisey"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Monday, November 21, 2016 1:48:51 PM
Subject: [openstack-dev] [kolla][kubernetes] kolla sla
78 matches
Mail list logo
