Hi,
I'm working on bug 1466451, which is about the invalid configuration of
property pci_passthrough_whitelist in nova.
My proposal for fixing this issue is:
Before start nova-compute sevice, do a precheck against /etc/nova/nova.conf
file, if the value format of pci_passthrough_whitelist
For writing a Jenkins Job you can refer *dsvm-cinder-driver.yaml.sample*
as a reference.
On Mon, Jul 20, 2015 at 12:04 PM, Tang Chen tangc...@cn.fujitsu.com wrote:
Hi Abhishek,
On 07/20/2015 02:09 PM, Abhishek Shrivastava wrote:
..
Quite a nice explanation +1 for all the things
Thanks Duncan. I was thinking if we can use volume_type instead of
available_zone totally. I mean whatever you have, one or many c-vol node,
you can just use volume_type to schedule volume creation on different
backends without using AZs at all. I also think available_zone is useless
if there is
Hey Yanis
On 07/17/2015 10:56 AM, Yanis Guenane wrote:
Hello everyone,
if set the value would have been set else it would default to upstream
default.
But Mathieu raised a fair point here[2] is that an empty string for some
settings is a valid value, and hence we can't rely on
it.
Since
Adrian,
Let's say someone creates a Hyper bay. The bay will be sth. like
BM+Hyper+Cinder+Neutron+k8s/mesos/swarm. This is exactly a mini HyperStack.
What nova does in this scenario is to provision the Hyper+BM hosts. Things like
LiveMigration, Multi-tenancy, Billing, VPC, Volume, etc., are
Hi Tang,
On Mon, Jul 20, 2015 at 11:18 AM, Tang Chen tangc...@cn.fujitsu.com wrote:
Hi Asselin, Abhishek,
Thanks for the reply. :)
On 07/19/2015 02:41 AM, Asselin, Ramy wrote:
HI Abhi Tang,
Sorry I missed this thread. Let me know if you’ve resolved your issues.
My repo is
Hi Abhishek,
On 07/20/2015 02:09 PM, Abhishek Shrivastava wrote:
..
Quite a nice explanation +1 for all the things you have done. Just one
more thing to ask, have you made your slave node static?
Not yet. And I haven't made my nodepool. :)
These are my next step.
But before I start
Hi, all.
I write a unit test in devstack and runs all tests okay on my environment.
Why does Jenkins failed when I upload my patch into review? The patch is
https://review.openstack.org/#/c/199588/. The failed test was named
Hi,
I deleted br-int and recreated br-int and found that those tap interfaces
of my instances were not added to br-int?
So I wonder what's the normal scenario?
How can I have my tap interfaces added to br-int?
Thanks
laocius
On 07/19/2015 02:41 AM, Asselin, Ramy wrote:
HI Abhi Tang,
Sorry I missed this thread. Let me know if you've resolved your issues.
My repo is undergoing migrations to reuse components in
openstack-infra/puppet-openstackci.
For single-use-nodes, the file you need has been removed here
Hi Zhi Chang,
You will have to use sorted to fix the test failure.
i.e., self.assertEqual(sorted(['2.2.2.2','1.1.1.1']),sorted(dns_list))
--Sridhar.
On 07/20/2015 11:17 AM, Zhi Chang wrote:
Hi, all.
I write a unit test in devstack and runs all tests okay on my
environment. Why does
On 17 July 2015 at 16:14, Kevin Carter kevin.car...@rackspace.com wrote:
I would like to nominate Matt Kassawara (IRC: sam-i-am) to the OpenStack
Ansible deployment core team. Matt has been instrumental in building out
our current install and use documentation[0], he is just about always in
Tap interfaces were added to br-int by libvirt.
I hard rebooted my VMs and tap interfaces were added to br-int successfully.
On Mon, Jul 20, 2015 at 4:01 PM, TAO ZHOU angelo...@gmail.com wrote:
Hi,
I deleted br-int and recreated br-int and found that those tap interfaces
of my instances were
On Thu, Jul 16, 2015 at 10:53 PM, Andrew Woodward xar...@gmail.com wrote:
Regardless of computing all the routes, we need to compute same role, but
multi-segement routes. In this case I see that nodegroups becomes
redundant. It's only value is that it may be a simpler interface then
templates
Hi,
This is a reminder that we’ll have a team meeting today at
#openstack-meeting at 16.00 UTC.
Agenda:
- Review action items
- Current status (progress, issues, roadblocks, further plans)
- Execution expiration policy discussion
- Open discussion
Add your own items either by
I think that volume types and AZs do quite different jobs, and should be
used for different things.
AZs are (in my opinion/understanding) about failure domains - ideally
they'd be mapped to redundancy in power/networking/etc - failures in one AZ
/shouldn't/ bring down a different AZ. This can't
Hello Cinder,
Instead of reverting nearly everything what was done (and is currently ongoing).
I would strongly suggest to simply reduce the number of the classes stepwise.
I spend some time to analyze what it actually implemented for all the drivers.
Please see:
I am not completely sure, but I believe that the primary associations
are that:
- a port is attached to a particular network
- a network may have an IPv4 subnet and/or an IPv6 subnet
- therefore, when a port is created, it gets an IPv4 address, and/or an
IPv6 address, according to the
On Sun, Jul 19, 2015 at 02:26:32PM EDT, Jim Rollenhagen wrote:
For a little background, this patch came from code that is running in
production today, where we're trunking two VLANs down to the host -- it
isn't a theoretical use case.
Have you taken a look at the vlan transparent API
inline
On 14.07.2015 18:59, Alec Hothan (ahothan) wrote:
inline...
On 7/8/15, 8:23 AM, Bogdan Dobrelya bdobre...@mirantis.com wrote:
I believe Oleksii is already working on it.
On all above I believe it is best to keep oslo messaging simple and
predictable, then have apps deal
Alex,
Yes, spec is much better place to introduce this. BTW, perestroika builds
new package for every commit and patch set and publishes them via HTTP.
Please check here
On 07/06/15 23:19, Ruby Loo wrote:
On 1 July 2015 at 08:25, Matt Keenan matt.kee...@oracle.com
mailto:matt.kee...@oracle.com wrote:
Hi,
In submitting my first ironic spec, I am following the process
outlined at:
https://wiki.openstack.org/wiki/Ironic/Specs_Process
As of
Hi,
Unshelving a volume backed instance was not working before merging the patch
[1].
In case of volume backed instance, snapshot is not taken when an instance is
shelved,
so shelve_image_id key is not set to the instance system metadata.
If shelve_image_id is None, UnshelveException was
Thanks for Sridhar. I separate the code by your comments. It can resolve this
problem. ;-D
Thanks
Zhi Chang
-- Original --
From: Sridhar Gaddamsgad...@redhat.com;
Date: Mon, Jul 20, 2015 05:16 PM
To: OpenStack Development Mailing List (not for usage
On Wed, Jul 15, 2015 at 6:11 PM, Mike Dorman mdor...@godaddy.com wrote:
I have been meaning to ask you about this, so thanks for posting.
I like the approach. Definitely a lot cleaner than the somewhat
hardcoded dependencies and subscriptions that are in the modules now.
Do you
On Mon, Jul 20, 2015 at 12:56:10PM +, Sean M. Collins wrote:
On Sun, Jul 19, 2015 at 02:26:32PM EDT, Jim Rollenhagen wrote:
For a little background, this patch came from code that is running in
production today, where we're trunking two VLANs down to the host -- it
isn't a theoretical
Madhuri,
I understand that you are somewhere in APAC. Perhaps it would be best
to set up a debugging session on Tuesday night -- at 9:30 pm EST
This would correspond to 01:30:00 a.m. GMT (Wednesday), which should
correspond to sometime in the morning for you.
We can start with the initial
Jaime,
Usually that's the error you see if you're trying to start up multiple API
processes. They all try and bind to port 9001, so that error is saying the API
can't bind. So something else (I suspect another designate-api process, or some
other type of API) is already listening on that
On 7/20/15, 05:16, Jesse Pretorius jesse.pretor...@gmail.com wrote:
On 17 July 2015 at 16:14, Kevin Carter kevin.car...@rackspace.com wrote:
I would like to nominate Matt Kassawara (IRC: sam-i-am) to the OpenStack
Ansible deployment core team. Matt has been instrumental in building out
our
I'd prefer not to multiply entities beyond necessity.
This is just a channel name - and a known name already. We can't just
rename it, we'll have to maintain both channels for some (significant)
amount of time. And this is usually bad: when you remember that there was
some discussion and want to
I've followed instructions to install Designate in Dev environment:
http://docs.openstack.org/developer/designate/install/ubuntu-dev.html
I've made some slight modifications to use qpid (instead of rabbitmq) and
to integrate with Infoblox.
What I've seen is that designate-api process dies (the
I found that paramiko does support proxies [1].
I remember looking at this a long time ago and you should be able to update
zuul code to use it [2].
Ramy
[1] http://blog.adimian.com/2014/10/paramiko-and-corporate-proxies/
[2]
Is this to optimize the performance of the job? Can you provide a link to where
the downloading is occurring that you’d like to restrict?
From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: Sunday, July 19, 2015 10:53 PM
To: OpenStack Development Mailing List (not for usage
Pull Requests are welcomed.
I think you’re referring to [1], but it shouldn’t make a functional difference
since ‘name’ is not being referenced anywhere.
[1]
https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/projects.yaml#L2
From: Tang Chen
Hi,
Yes please do. Could you file a lp bug for it? It seems to me to be a good
candidate for a scenario test.
Thank you
Andrea
On Mon, 20 Jul 2015 1:45 pm Deore, Pranali11 pranali11.de...@nttdata.com
wrote:
Hi,
Unshelving a volume backed instance was not working before merging the
On Mon, Jul 20, 2015 at 2:41 PM, Deore, Pranali11
pranali11.de...@nttdata.com wrote:
Hi,
Unshelving a volume backed instance was not working before merging the
patch [1].
In case of volume backed instance, snapshot is not taken when an instance
is shelved,
so shelve_image_id key is
On 07/19/2015 09:42 PM, Emilien Macchi wrote:
I'm currently in holidays but I could not resist to take some time and
reply.
On 07/18/2015 06:32 PM, Dmitry Borodaenko wrote:
It has been 5 weeks since Emilien has asked Fuel developers to
contribute more
actively to Puppet OpenStack project [0].
On 07/20/2015 07:16 AM, Marc Koderer wrote:
Hello Cinder,
Instead of reverting nearly everything what was done (and is currently
ongoing).
I would strongly suggest to simply reduce the number of the classes stepwise.
This makes sense, and this was the general plan as I recall -- to
On 7/15/15, 9:18 AM, Ed Leafe e...@leafe.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Changing the architecture of a complex system such as Nova is never
easy, even when we know that the design isn't working as well as we
need it to. And it's even more frustrating because when the
Hi Tim,
I only start one api process. In fact, when I say that the api process
dies, I don't have any designate-api process and there is no process
listening on the 9001 port.
When I started all the designate processes, the API worked correctly
because I had tested it. But after some inactivity
On 07/17/15 03:17, Yan Xing'an wrote:
For example, in usecase of VM is a LVS (Linux Virtual Server),
to make any client's ip outgoing, we need configure allowed_address_pairs to
0.0.0.0/0,
or disable security-group on port by setting port-security-enable false.
After that, mac-level rules
Alex,
As I've just found out this package available here [1] is not actually
build with your patch (instead it is from previous successful build). Looks
like perestroika can not build this package due to some environment
related issues. I've poked Dmitry Burmistrov to check it out.
However, your
Excerpts from Jesse Cook's message of 2015-07-20 07:48:46 -0700:
On 7/15/15, 9:18 AM, Ed Leafe e...@leafe.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Changing the architecture of a complex system such as Nova is never
easy, even when we know that the design isn't working
Got my ticket, thanks Joe / Rackspace for hosting this :)
Thanks,
Kiall
On 20/07/15 18:05, Joe Mcbride wrote:
Hello,
The Designate team will hold it's mid-cycle meet-up in August, details below.
- Dates: August 17 to 20, 2015
- Location: Austin TX
- Registration/agenda:
On 07/17/2015 07:55 PM, Jamie Lennox wrote:
So I'm not familiar with how Sahara handles contexts however from a theoretical
stand point anything that is defined in config should be able to be cached
globally. So service specific sessions, and admin auth. The context typically
would contain
On 07/20/2015 11:24 AM, Alex Schultz wrote:
As a new contributor to any openstack project, this is the first thing I
do. Find out when the weekly meetings is, attend and monitor the
conversion. Almost always there is an open discussion at the end of the
weekly business.
Going back through
Hi Ian,
On 20/07/15 18:00, Ian Wells wrote:
On 19 July 2015 at 03:46, Neil Jerram neil.jer...@metaswitch.com
mailto:neil.jer...@metaswitch.com wrote:
The change at [1] creates and describes a new 'routed' value for
provider:network_type. It means that a compute host handles data
Love the idea, great explanation! I see value in this going forward.
Definitely interested.
From: Chen, Shaoquan sean.ch...@hp.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 07/19/2015 05:34 PM
Subject:
Excerpts from Ed Leafe's message of 2015-07-19 18:37:49 -0500:
On Jul 16, 2015, at 4:13 AM, Thierry Carrez thie...@openstack.org wrote:
I don't really like the idea of a popularity contest to define HA or
scales -- anyone with a stake in the game and their cat will upvote or
downvote for
Excerpts from Sam Stoelinga's message of 2015-07-18 05:39:23 -0700:
+1 on Kevin Benton's comments.
Ironic should have integration with switches where the switches are SDN
compatible. The individual bare metal node should not care which vlan,
vxlan or other translation is programmed at the
Hi
I'm new to openstack development, hoping to contribute. I plan to start
out by updating UT cases from mox to mock. Just set up a development
environment on Windows VirtualBox Ubuntu 14.04, and used the following to
get the dependencies (plus apt-get python3-dev, which wasn't in this script
On Fri, Jul 17, 2015 at 7:32 AM, Victor Stinner vstin...@redhat.com wrote:
Hi,
...
(3) keystonemiddleware: blocked by python-memcached, I sent a pull request
3 months ago and I'm still waiting...
https://github.com/linsomniac/python-memcached/pull/67
I may fork the project if the
On 20 July 2015 at 10:21, Neil Jerram neil.jer...@metaswitch.com wrote:
Hi Ian,
On 20/07/15 18:00, Ian Wells wrote:
On 19 July 2015 at 03:46, Neil Jerram neil.jer...@metaswitch.com
mailto:neil.jer...@metaswitch.com wrote:
The change at [1] creates and describes a new 'routed' value
Dmitry and I chatted some this morning and I'd at least like to address
those issues so that we can resolve them and move on to the other
discussions. I am not speaking for Emilien here, just jumping in as a core
and trying to help resolve some of this.
As Emilien notes, many of us do not work
This week we will be releasing 2.0 versions of oslo.config,
oslo.messaging, and oslo.utils. These are the last three libraries still
using the 'oslo' import namespace. The changes have been tested in the
gate as part of merging them into the libraries, and I have been running
unit tests for all of
Hello,
The Designate team will hold it's mid-cycle meet-up in August, details below.
- Dates: August 17 to 20, 2015
- Location: Austin TX
- Registration/agenda:
http://www.eventbrite.co.uk/e/openstack-designate-2015-summer-mid-cycle-meetup-tickets-17833181526
- Remote attendees are welcome
First of all, your network contains an IPv4 and an IPv6 SLAAC subnet.
Given the the definition of SLAAC, your port will receive an IPv6 address
from the Ipv6 subnet. On the other hand, if you want your network to have
both IPv6 and IPv4, and want to selectively assign either IPv4 or IPv6 to
your
@Elena,
What are the pro's and con's of having a handler as this was the
existing behavior for all the projects that picked up code from
oslo-incubator for this behavior?
-- dims
On Mon, Jul 20, 2015 at 1:12 PM, Elena Ezhova eezh...@mirantis.com wrote:
Hi!
Not so long ago oslo.service had a
Vladimir,
Thanks. Can you point me to the error for perestroika? I'd be happy to
take a look as well. I spent most of Friday throwing various options at the
CI system to try and figure out how to get the spec to work with the CI
fuel-library package building so perhaps there's a different way to
Thanks for joining the meeting today!
Meeting minutes:
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-07-20-16.00.html
Meeting log:
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-07-20-16.00.log.html
The next meeting will be on July 27. You can post your
Side Question: Is is normal for QPid to log all the
\x0f\x01\x00\x14\x00\x01\x00\x00\x00\x00\x00's etc?
I'm guessing that, since you're using qpid, you're also on RedHat. Could
RH's SELinux policies be preventing the service from binding to tcp/9001?
If you start as root, do you see similar
As a new contributor to any openstack project, this is the first thing I
do. Find out when the weekly meetings is, attend and monitor the
conversion. Almost always there is an open discussion at the end of the
weekly business.
Going back through the last 5 weeks of irclogs[1], I couldn't
Hi Mike,
We have moved all CIs on cinder patches after testing on sandbox.
We will be in touch with infra-team and cinder team to make CIs more robust
and spam-free.
Regards
Nikesh
On Fri, Jul 17, 2015 at 9:45 PM, Nikesh Kumar Mahalka
nikeshmaha...@vedams.com wrote:
Hi Mike,
We are taking
I'm looking for feedback from anyone interest but, in particular, I'd
like feedback from the following people for varying perspectives:
Mark McClain (proposed alternate), John Belamaric (IPAM), Ryan Tidwell
(BGP), Neil Jerram (L3 networks), Aaron Rosen (help understand
multi-provider networks) and
Hi John ,
Thanks a lot John for your response.
I tried executing the script with the following options before , but it
seems it did not work .Hence tried with the curly baraces .
Please find other options below :
[root@HSM-Client bin]# python pkcs11-key-generation --library-path
On Sun, Jul 19, 2015 at 11:43 AM, Jay Pipes jaypi...@gmail.com wrote:
On 07/15/2015 03:27 PM, John Griffith wrote:
It's relatively limited right now I think, and part of the reason for
that is we've tried to ensure that the information that we put on tags
is subjective
I think you mean
A late notice but here's the agenda for tomorrow's meeting. Emilien is out
so I will be running it. There's not a big agenda so if you have bugs you'd
like to go into please bring them.
https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150721
See you tomorrow
Resend, fixed subject.
tox -e py34 succeeds, btw.
Hi
I'm new to openstack development, hoping to contribute. I plan to start
out by updating UT cases from mox to mock. I just set up a development
environment on Windows VirtualBox Ubuntu 14.04, and used the following to
get the
-1
We started using API versioning specifically to be able to introduce
breaking changes. If we disallow this, the whole versioning will become
even more pointless.
What concerns you is the one of the downsides of feature hiding that I was
talking about for a long time, and nobody seemed to
On 07/20/2015 02:04 PM, Clint Byrum wrote:
Excerpts from Chris Friesen's message of 2015-07-20 12:17:29 -0700:
Some questions:
1) Could you elaborate a bit on how this would work? I don't quite understand
how you would handle a request for booting an instance with a certain set of
Hi,
I'm hoping to design a FUEL plugin which can provision a switch or set
of switches according to the Network Settings specified when first
configuring an environment in FUEL.
We have puppet manifests which allow us to configure every aspect
of our switches, including the plumbing of VLANs. It
I have a feeling that we really need to make whatever this selection
process has clearly defined API boundaries, so that various
'implementation experiments' can be used (and researched on).
Those API boundaries will be what scheduling entities must provide but
the implementations could be
On 7/20/15, 5:24 AM, Bogdan Dobrelya bdobre...@mirantis.com wrote:
inline
On 14.07.2015 18:59, Alec Hothan (ahothan) wrote:
inline...
On 7/8/15, 8:23 AM, Bogdan Dobrelya bdobre...@mirantis.com wrote:
I believe Oleksii is already working on it.
On all above I believe it is
On Fri, Jul 17, 2015 at 7:32 AM, Victor Stinner vstin...@redhat.com wrote:
Hi,
We are close to having a voting py34 gate on all OpenStack libraries and
applications. I just made the py34 gate voting for the 5 following projects:
* keystone
...
Victor
While there's a py34 gate for
Hmm... This error is usually because one of the parameters is an incorrect
type. I'm wondering if the length is coming through as a string instead of an
integer. As the length defaults to 32, try not specifying the length parameter.
If that works, we need to report a defect to make sure that
Folks,
It took a while for us to get here, with today's 2.0.0 releases of
oslo.utils, oslo.config and oslo.messaging, we are finally getting rid
of the oslo namespace usage as documented in:
http://specs.openstack.org/openstack/oslo-specs/specs/kilo/drop-namespace-packages.html
Thanks to Doug
On Sat, Jul 18, 2015 at 5:42 AM Sam Stoelinga sammiest...@gmail.com wrote:
+1 on Kevin Benton's comments.
Ironic should have integration with switches where the switches are SDN
compatible. The individual bare metal node should not care which vlan,
vxlan or other translation is programmed at
Having Nova make assumptions isn't the right way to do this though. To
support this I would rather see an ML2 driver that informs Nova to pass
tagging info to the instance via the port binding info. Only neutron knows
which one is appropriate based on the network configuration.
On Jul 20, 2015
Ya, that makes sense now that you mention it. We will still need node
groups to act as partitioning for the rack values
On Mon, Jul 20, 2015 at 1:44 AM Sergey Vasilenko svasile...@mirantis.com
wrote:
On Thu, Jul 16, 2015 at 10:53 PM, Andrew Woodward xar...@gmail.com
wrote:
Regardless of
On 07/20/2015 11:40 AM, Clint Byrum wrote:
To your earlier point about state being abused in the system, I
totally 100% agree. In the past I've wondered a lot if there can be a
worker model, where compute hosts all try to grab work off queues if
they have available resources. So API requests
So, as you know, I think that a breaking change like this is really bad for
our users, no matter how loudly we declare it or when we do it. Version
negotiation in the REST API doesn't give us license to do this. I also
think most users should not need to know the version number at all, should
be
Excerpts from Chris Friesen's message of 2015-07-20 12:17:29 -0700:
On 07/20/2015 11:40 AM, Clint Byrum wrote:
To your earlier point about state being abused in the system, I
totally 100% agree. In the past I've wondered a lot if there can be a
worker model, where compute hosts all try to
On 20 July 2015 at 15:33, Ian Cordasco ian.corda...@rackspace.com wrote:
Yes, Matt should be doing more reviews. The difference is that (as I
understand it) we want to include Matt as a documentation core more than
as a core reviewer for playbooks. Matt's reviews have all pertained to
On 19 July 2015 at 03:46, Neil Jerram neil.jer...@metaswitch.com wrote:
The change at [1] creates and describes a new 'routed' value for
provider:network_type. It means that a compute host handles data
to/from the relevant TAP interfaces by routing it, and specifically
that those TAP
Hi!
Not so long ago oslo.service had a handler for SIGINT and on receiving this
signal a process killed all children with SIGTERM and exited.
Change [1], that added graceful shutdown on SIGTERM, removed all SIGINT
handlers and currently all services that consume oslo.service generate
Hi guys,
did we enable SSL for Fuel Master node and OpenStack REST API endpoints by
default? If not, let's enable it by default. I don't know why we should not.
Looks like we need to update blueprints as well [1], [2], as they don't
seem to reflect current status of the feature.
[1]
Hi all,
I have configured these lines in my devstack localrc
# Load the external LBaaS plugin.
enable_plugin neutron-lbaas
https://git.openstack.org/openstack/neutron-lbaas
## Neutron - Load Balancing
ENABLED_SERVICES+=,q-lbaasv2
# Horizon (Dashboard UI) - (always
Currently horizon doesn’t support LBaaS v2, there is a blueprint related
but it doesn’t implement yet:
https://blueprints.launchpad.net/horizon/+spec/lbaas-v2-panel
2015-07-21 9:49 GMT+08:00 jiangshan0...@139.com jiangshan0...@139.com:
Hi all,
I have configured these lines in my
Excerpts from Chris Friesen's message of 2015-07-20 14:30:53 -0700:
On 07/20/2015 02:04 PM, Clint Byrum wrote:
Excerpts from Chris Friesen's message of 2015-07-20 12:17:29 -0700:
Some questions:
1) Could you elaborate a bit on how this would work? I don't quite
understand
how you
All,
I’m pleased to announce the 4th component merged to puppet-openstackci repo [1].
This means 3rd party ci operators can now use the same scripts that the
OpenStack Infrastructure team uses in the official ‘Jenkins’ CI system for:
1. Log Server
2. Jenkins
3. Zuul
4.
Hi Alee,
Thank you for showing up for help.
The proposed timing suits me. It would be 10:30 am JST for me.
I am madhuri on #freenode.
Will we be discussing on #openstack-containers?
Sdake,
Thank you for setting up this.
Regards,
Madhuri
On Mon, Jul 20, 2015 at 11:26 PM, Ade Lee
- Original Message -
I'm looking for feedback from anyone interest but, in particular, I'd
like feedback from the following people for varying perspectives:
Mark McClain (proposed alternate), John Belamaric (IPAM), Ryan Tidwell
(BGP), Neil Jerram (L3 networks), Aaron Rosen (help
Thanks Duncan! It make me clearer about AZ, and I agree with you that we
should work on making users/admins know how to use AZ and volume_type
correctly.
2015-07-20 17:27 GMT+08:00 Duncan Thomas duncan.tho...@gmail.com:
I think that volume types and AZs do quite different jobs, and should be
There are two routed network models:
- I give my VM an address that bears no relation to its location and ensure
the routed fabric routes packets there - this is very much the routing
protocol method for doing things where I have injected a route into the
network and it needs to propagate. It's
Excerpts from Joshua Harlow's message of 2015-07-20 14:57:48 -0700:
I have a feeling that we really need to make whatever this selection
process has clearly defined API boundaries, so that various
'implementation experiments' can be used (and researched on).
Those API boundaries will be
Clint Byrum wrote:
Excerpts from Chris Friesen's message of 2015-07-20 14:30:53 -0700:
On 07/20/2015 02:04 PM, Clint Byrum wrote:
Excerpts from Chris Friesen's message of 2015-07-20 12:17:29 -0700:
Some questions:
1) Could you elaborate a bit on how this would work? I don't quite understand
Hi all,
My apologies, but I won't be able to attend the IRC meeting tonight.
The agenda is very light (basically non-existent) so I suggest that we just
cancel it and meet next Monday.
Also, I haven't seen any response to my email (*) from one week ago about
the lack of attendance to this (late
Steven,
I believe your question is covered by [0] blueprint.
[0]
https://github.com/stackforge/fuel-specs/blob/master/specs/7.0/role-as-a-plugin.rst
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Mon, Jul 20, 2015 at 2:49 PM, Steven Kath k...@linux.com wrote:
Hi,
I'm
Hi Ramy,
- The project list is mentioned in the *devstack-vm-gate-wrap*
script[1].
- Downloaded using *functions.sh* script using *setup workspace*
function[2]
[1]
https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate-wrap.sh#L35
[2]
I found this after noon that fuel-web CI was broken due to the recent
release of oslo.config and oslo.utils 2.0.0 [1]
I attempted to muck around with the pinning of the requirements.txt and had
initial success with it [2] but later found that it's failing the
test_check_requirements_conflicts
1 - 100 of 101 matches
Mail list logo
