Hi,
Just wondering what is fine result and decision? This change is pretty wide and
impacts many dev (and users), I think we should be listening to the feedback
before making any decision.
Regards,
> On 17 Dec 2015, at 11:01, Artem Silenkov wrote:
>
> Hello!
> We
I agree with Evgeny: from work organization it would more optimal to have 2
repos. API and system facing programming are completely different domains,
requiring different skill sets. In my opinion separation would lower the entry
barriers.
Regards,
> On 17 Dec 2015, at 15:53, Evgeniy L
Have a look at extra-route extension.
http://developer.openstack.org/api-ref-networking-v2-ext.html#extraroute-ext
On Mon, Dec 28, 2015 at 9:10 AM, Vikram Choudhary wrote:
>
>
> On Mon, Dec 28, 2015 at 10:20 PM, Jay Pipes wrote:
>
>> On 12/28/2015
The next TripleO IRC meeting will be on January 5th 2016.
Thanks,
Dan
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
Hi Gal, you reverted this patch [1] due to the broken pipeline. Could
you provide some debug information or detailed description? When I run
my devstack, I cannot reproduce the sync problem.
[1]
https://github.com/openstack/dragonflow/commit/f83dd5795d54e1a70b8bdec1e6dd9f7815eb6546
--
Li Ma
On Tue, Dec 29, 2015 at 2:34 AM, Chandra Mohan Babu Nadiminti <
nadiminti.chan...@gmail.com> wrote:
> Have a look at extra-route extension.
>
>
> http://developer.openstack.org/api-ref-networking-v2-ext.html#extraroute-ext
>
Vikram: IIUC, extra-route can only re-direct the traffic to a specific
After seeing that vYatta requires a driver plugged in to the interface,
i gave up debugging it.
Now i am trying vArmour driver. Looks simpler. Many things are clearer
except from that they have their own L3 agent. It sees it should be
enabling API calls when a new router is added, removed or
Hi All,
We want to redirect all / some specific traffic incoming traffic to a
particular port where a network function is deployed. [Network function
could be DPI, IDS, Firewall, Classifier, etc]. In this regard, we have few
queries:
1. How this can be achieved?
2. Do we have well-defined NBI's
On 12/28/2015 05:03 AM, hao wang wrote:
> hi, Janice
>
> This idea seems to me that is useful to detect the state of
> cinder-volume process more quickly, but I feel there is another issue
> that if the back-end device go to fail you still
> can't keep cloud in ha or create volume successfully
Hi All,
Thanks alot for your valuable feedback Jesse.
Point 1 :
I have made the appropriate Designate entry in the file here :
/playbooks/defaults/repo_packages/openstack_services.yml and uploaded it for
review here :
On 17/12/15 19:34 +, Flavio Percoco wrote:
On 09/12/15 18:52 -0430, Flavio Percoco wrote:
Greetings,
To all Glance drivers and people interested in following up on Glance
specs. I've added to our meeting agenda etherpad[0] the list of review
priorities for specs.
Please, bare in mind that
Hi Li Ma,
I think its a good idea.
I suggest for first stage, pass the CONF as optional parameter in addition
to the db_ip and db_port.
This way you will have minimum code changes at first patch.
If we see its working ok, we can later remove db_ip and db_port and adjust
the other
drivers in
Hi,
> I want to propose not to wipe disks and simply unset bootable flag from
node disks.
AFAIK, removing bootable flag does not guarantee that system won't be
booted from the local drive. This is why erase_node is needed.
Regards,
Alex
On Fri, Dec 25, 2015 at 8:59 AM, Artur Svechnikov
Great! Can't wait to see you guys :)
2015-12-28 10:03 GMT+08:00 Qiming Teng :
> Dear all,
>
> Wish you all a merry christmas and a happy new year.
>
> Senlin team is planning a mid-cycle meetup next month in Beijing. Well,
> it goes beyond just a meetup between
Hello,
I added some items to our agenda:
https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151229
Feel free to add more topics, reviews, bugs, etc.
Some people are around this week so we will make our weekly meeting
tomorrow at UTC 1500.
See you there,
On 12/22/2015 09:42 AM,
On 12/22/2015 12:38 PM, Dougal Matthews wrote:
> Hi all,
>
> I mentioned this at the meeting last week, but wanted to get wider
> input. As far as I can tell from the current activity, there is no work
> going into Tuskar and it isn't being tested with CI. This means the code
> is becoming more
Hi Sergii,
You've raised an old thread started by Oleg G. once again [1]. Last
time we didn't reach any agreements, but I'm sure that it would be
better to change version into "liberty-8.0" instead of "2015.2.0-8.0".
What do you think? It could be done easily with two patches - one to
nalgun,
Hi there,
The gate for telemetry projects is broken:
https://bugs.launchpad.net/heat/+bug/1529583
The failure appears in Heat from what I understand:
BadRequest: Expecting to find domain in project - the server could not
comply with the request since it is either malformed or otherwise
On 23.12.2015 18:50, Matthew Mosesohn wrote:
> I agree. As far as I remember, rabbit needs fqdns to work and map
> correctly. I think it means we should disable the ability to move the
> internal messaging network role in order to fix this bug until we can
> add extra dns entries per network role
Hi, Julien.
I suppose, that your guess is right.
Mentioned patch was merged recently and it broke our Ceilometer related
functional test.
There is a patch, which skip it. [1] and related bug [2]
We already have a revert for this staff [3] and patch for check based on
this revert [4].
[1]
> Hi there,
>
> The gate for telemetry projects is broken:
>
> https://bugs.launchpad.net/heat/+bug/1529583
>
> The failure appears in Heat from what I understand:
>
> BadRequest: Expecting to find domain in project - the server could not
> comply with the request since it is either
On Mon, Dec 28 2015, Rabi Mishra wrote:
> Yes, this has started happening after keystone/trusts config changes by the
> devstack patch you mentioned. I've no idea how this can be fixed. As Steve
> Hardy is away, either someone with keystone knowledge should fix this or we
> merge the devstack
Hi!
This has been implemented: the Artifacts subteam meeting is moved to 17:00
UTC Mondays by patch [1].
However, since we are still deep in the holiday season (and the significant
part of the team will be on PTO during the whole next week), I propose to
cancel both todays' and the next week's
Hi team,
We will not be holding our weekly IRC meeting on December 29 due to holidays.
We will convene again on January 5.
Regards,
Devdatta
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Team,
We’re cancelling the team meeting today since a number of key team members
won’t be able to attend.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Thanks for your help, Vladimir. You are right, now that I look more closely, in
dhcpv6-stateful mode the default gateway is acquired through router
advertisement (instead of dhcp6 options). And the default gateway I get is the
link-local address instead of the configured gateway_ip of
On 12/24/2015 02:30 PM, Clint Byrum wrote:
This is entirely philosophical, but we should think about when it is
appropriate to adopt which mode of operation.
There are basically two ways being discussed:
1) Fail fast.
2) Retry forever.
Fail fast pros- Immediate feedback for problems, no
In order to ensure that LVM can be configured as desired, its necessary to
purge them and then reboot the node, otherwise the partitioning commands
will most likely fail on the next attempt as they will be initialized
before we can start partitioning the node. Hence, when a node is removed
from
Hey,
So one thing we need to consider there is that currently 3 options we
support (binary+souce centos and source ubuntu) basically behaves the
same way - it install current master (or last nights master, which is
close enough). This one will have fundamentally different behavior,
and we need to
On Mon, Dec 28, 2015 at 10:20 PM, Jay Pipes wrote:
> On 12/28/2015 11:13 AM, Vikram Choudhary wrote:
>
>> Hi All,
>>
>> We want to redirect all / some specific incoming traffic to a particular
>> neutron port, where a network function is deployed. [Network function
>> could
Hey folks,
I have received significant feedback that the lack of Ubuntu binary support is
a problem for Kolla adoption. Still, we had nobody to do the work, so we held
off approving the blueprint. There were other reasons such as:
* There is no delorean style repository for debian
>
>
> It's used in stop_deployment provision stage [0] and for control reboot
> [1].
>
> > Is it a fall back mechanism if the mcollective fails?
>
> Yes it's like fall back mechanism, but it's used always [2].
>
As I remember it the use of SSH for stopping provisioning was because of
our use of
On 12/28/2015 11:13 AM, Vikram Choudhary wrote:
Hi All,
We want to redirect all / some specific incoming traffic to a particular
neutron port, where a network function is deployed. [Network function
could be DPI, IDS, Firewall, Classifier, etc]. In this regard, we have
few queries:
1. How we
Another data point.. I've had to work around daemons failing fast as discussed
below when working with docker-compose. It doesn't have nice dependency
handling yet, and during the initial bootstrap of all the containers in a pod,
some can fail due to not sticking around long enough for the
On Mon, Dec 28, 2015 at 1:13 AM Bogdan Dobrelya
wrote:
> On 23.12.2015 18:50, Matthew Mosesohn wrote:
> > I agree. As far as I remember, rabbit needs fqdns to work and map
> > correctly. I think it means we should disable the ability to move the
> > internal messaging
Hi All,
We want to redirect all / some specific incoming traffic to a particular
neutron port, where a network function is deployed. [Network function could
be DPI, IDS, Firewall, Classifier, etc]. In this regard, we have few
queries:
1. How we can achieve this?
2. Do we have well-defined NBI's
>We could just state we wont block any activity on the Debian binary
release (this includes tagging, releasing, etc)
I think thats key. If cloud-archive is available before we tag then
fantastic, but I don't want to hold it up because of this. Additionally, we
could do experimental gates for this
On 12/23/2015 08:35 PM, Morgan Fainberg wrote:
On Wed, Dec 23, 2015 at 10:32 AM, Jay Pipes > wrote:
On 12/23/2015 12:27 PM, Lars Kellogg-Stedman wrote:
I've been looking into the startup constraints involved when
launching
Hi everyone,
The OpenStack Infrastructure (Infra) team is not skipping meetings
through the end of month holidays, so we are having our next weekly
meeting as scheduled on Tuesday December 29th, at 19:00 UTC in
#openstack-meeting
Meeting agenda available here:
The Horizon mid-cycle sprint is in Hillsboro, Oregon Feb 23-25 and
hosted at the Intel site in Hillsboro just west of Portland.
The wiki for the mid-cycle sprint is
https://wiki.openstack.org/wiki/Sprints/HorizonMitakaSprint
Please note your intention to attend on the wiki page.
Thanks,
David
Hi Li Ma,
I haven't investigated the root problem yet as i seen it at the end of day
yesterday.
However if you look at this test : https://review.openstack.org/#/c/261997/
it verify that the correct number of flows
are installed after a clean devstack process.
What i noticed with this patch is
Excerpts from Jay Pipes's message of 2015-12-28 09:45:39 -0800:
> On 12/24/2015 02:30 PM, Clint Byrum wrote:
> > This is entirely philosophical, but we should think about when it is
> > appropriate to adopt which mode of operation.
> >
> > There are basically two ways being discussed:
> >
> > 1)
+1 for "fuel: recheck". A nice to have addition would be:
"fuel: recheck verify-fuel-library-tasks"
to retrigger just one failed job.
--
Dmitry Borodaenko
On Mon, Nov 23, 2015 at 01:32:35PM +, Bob Ball wrote:
> There was a conversation a while ago around explicitly avoiding the empty
>
Hello everyone,
Just wanted to give you all some progress update at what we have been doing
in Kuryr,
We conducted an IRC meeting today, you can see the logs here [1]
1) We got Docker pluggable IPAM support in Kuryr thanks to Vikas Choudhary,
there
are still some small points to address but
One more argument in favour of abandoning use of milestones is that they do not
work well with new stable branch release structure and us having multiple
repositories rely on one launchpad. We might have murano ver 1.0.5 and
murano-dashboard ver 1.0.3, which would be totally fine under current
45 matches
Mail list logo