Hi all,
I have been trying to set up an openstack environment using vagrant and
packstack. I provisioned a Fedora-19 VM through vagrant and used a shell
script to take care of installation and other things. The first thing that
shell script does is "yum install -y openstack-packstack" and then
To summarize:
Certificate will be a first level citizen which can be reused and
For certificate management nothing sophisticated is required.
Can you please Vote (+1, -1)?
We can move on if there is consensus around this.
> -Original Message-
> From: Stephen Gran [mailto:stephen.g...@g
Hello Jay,
Just in case you've missed it, there is a project Savanna dedicated to
deploying Hadoop clusters on OpenStack:
https://github.com/openstack/savanna
http://savanna.readthedocs.org/en/0.3/
Dmitry
2013/11/29 Jay Lau
> Hi,
>
> I'm now trying to deploy a hadoop cluster with heat, just
On Fri, Nov 29, 2013 at 8:24 AM, Roman Bogorodskiy
wrote:
> Hello,
>
> Yes, libvirt's qemu driver works almost fine currently, except the fact that
> it
> needs a 'real' bridge driver, so all the networking configuration like
> filtering rules, NAT, etc
> could be done automatically, like for Linu
> > The first stage is technical - move Nova scheduling code from A to be.
> > What do we achieve - not much - we actually complicate things - there
> > is always churn in Nova and we will have duplicate code bases. In
> > addition to this the only service that can actually make use of they
> > is
Hi Trinath
Please find the server.log and neutron.conf
* **
server.log
-
2013-11-29 11:21:45.276 13505 INFO neutron.common.config [-] Logging enabled!
2013-11-29 11:21:45.277 13505 WARNING neutron.common.legacy [-] Old
cla
On 2013/20/11 01:23, Stefano Maffulli wrote:
On 11/19/2013 08:19 AM, Julie Pichon wrote:
I've been thinking about the AskBot UX website [0] and its lack of
visibility, particularly for new community members.
Indeed, it's one of the drawbacks of splitting groups: information tends
not to flow v
On Fri, Nov 29, 2013 at 2:25 PM, Jian Wen wrote:
> I don't think we can implement a stateful firewall[1] now.
I don't think we need a stateful firewall, a stateless one should work
well. If the stateful conntrack is completed in the future, we can
also take benefit from it.
>
> Once connection t
Hi
Thankyou for the info, I downgraded sqlalchemy accordingly, but there
were lot of other dependencies I had to take care (as below). The
error which still continues to persist in my environment is :
RuntimeError: Unable to load quantum from configuration file
/etc/neutron/api-paste.ini.
are ther
Hi Paul,
I think you are missing routes on your host. AFAIK devstack adds a route to
the host for default private network. You might need this as well.
Thanks,
Eugene.
On Thu, Nov 28, 2013 at 1:14 AM, Paul Michali wrote:
> Hi,
>
> I had this working once, but after rebooting my host and resta
On 11/28/13 11:34 PM, "Robert Collins" wrote:
>On 29 November 2013 09:44, Gary Kotton wrote:
>>
>>
>> The first stage is technical - move Nova scheduling code from A to be.
>> What do we achieve - not much - we actually complicate things - there is
>> always churn in Nova and we will have dupl
Hi,
Do we need to update the jsonschema constraint in the requirements.txt? Many
tests are failing with jsonschema 1.3.0 with the same error.
==
FAIL:
nova.tests.test_api_validation.AdditionalPropertiesDisableTestCase.test_vali
On 11/27/2013 10:15 PM, Adrian Otto wrote:
On Nov 27, 2013, at 11:27 AM, Jay Pipes wrote:
On 11/27/2013 02:03 PM, Adrian Otto wrote:
Jay,
On Nov 27, 2013, at 10:36 AM, Jay Pipes
wrote:
On 11/27/2013 06:23 AM, Tom Deckers (tdeckers) wrote:
I understand the an Assembly can be a larger gro
Robert Collins wrote:
> https://etherpad.openstack.org/p/icehouse-external-scheduler
Just looked into it with release management / TC hat on and I have a
(possibly minor) concern on the deprecation path/timing.
Assuming everything goes well, the separate scheduler will be
fast-tracked through inc
Hey
Anyone got an update on this?
The keystone blueprint for KDS was marked approved on Tuesday:
https://blueprints.launchpad.net/keystone/+spec/key-distribution-server
and a new keystone review was added on Sunday, but it must be a draft
since I can't access it:
https://review.openstack.
Hello Sandy,
I'm very interested in performance results for Ceilometer. Now we have
successfully installed Ceilometer in the HA-lab with 200 computes and 3
controllers. Now it works pretty good with MySQL. Our next steps are:
1. Configure alarms
2. Try to use Rally for OpenStack performance with
On 11/28/2013 07:45 AM, Akihiro Motoki wrote:
Hi,
I am working on adding request-id to API response in Neutron.
After I checked what header is used in other projects
header name varies project by project.
It seems there is no consensus what header is recommended
and it is better to have some con
On Fri, Nov 29 2013, Nadya Privalova wrote:
> I'm very interested in performance results for Ceilometer. Now we have
> successfully installed Ceilometer in the HA-lab with 200 computes and 3
> controllers. Now it works pretty good with MySQL. Our next steps are:
What I'd like to know in both your
What are the expected delivery guarantees for messages for rpc
transports in oslo.messaging?
Are failures to be handled by the applications using the rpc interface
(e.g. by retrying on timeout)? Or is the transport expected to provide
the necessary reliability of messages? Or is this something
On 11/29/2013 10:33 AM, Jay Pipes wrote:
> On 11/28/2013 07:45 AM, Akihiro Motoki wrote:
>> Hi,
>>
>> I am working on adding request-id to API response in Neutron.
>> After I checked what header is used in other projects
>> header name varies project by project.
>> It seems there is no consensus wh
On 11/25/2013 12:39 PM, Georgy Okrokvertskhov wrote:
> Hi,
>
> Just for clarification for Windows images, I think Windows image
> creation is closer to Docker approach. In order to create a special
> Windows image we use KVM\QEMU VM with initial base image, then install
> all necessary component
Hi Abbass,
I am in the process of coding some of this now - take a look at
https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking - now
has a specification document attached
https://etherpad.openstack.org/p/IcehouseNovaExtensibleSchedulerMetrics - the
design summit session
On 11/29/2013 11:41 AM, Julien Danjou wrote:
> On Fri, Nov 29 2013, Nadya Privalova wrote:
>
>> I'm very interested in performance results for Ceilometer. Now we have
>> successfully installed Ceilometer in the HA-lab with 200 computes and 3
>> controllers. Now it works pretty good with MySQL. O
On 11/29/2013 11:32 AM, Nadya Privalova wrote:
> Hello Sandy,
>
> I'm very interested in performance results for Ceilometer. Now we have
> successfully installed Ceilometer in the HA-lab with 200 computes and 3
> controllers. Now it works pretty good with MySQL. Our next steps are:
>
> 1. Confi
Sandy,
Seems like we should think about how we can combine our approaches.
Rally makes load using python clients (e.g. ceilometer python client) using
different amount of users/tenatns/active_users/... So it address #2 point.
About profiling part.
Actually we attempted to make profiling system ba
On Fri, Nov 29 2013, Sandy Walsh wrote:
> For our purposes we aren't interested in the collector. We're purely
> testing the performance of the storage drivers and the underlying
> databases.
Then the connection would map to: with how many SQL connection are you
injecting things in the DB in para
We have a review up (https://review.openstack.org/#/c/58297/) to add some
features to the notification system in the oslo incubator. THe notification
system is being moved into oslo.messaging, and so we have the question of
whether to accept the patch to the incubated version, move it to
oslo.messa
> Based on that, I would like to say that we do not add new features to
> incubated code after it starts moving into a library, and only provide
> "stable-like" bug fix support until integrated projects are moved over to
> the graduated library (although even that is up for discussion). After all
>
Doug,
Based on that, I would like to say that we do not add new features to
incubated code after it starts moving into a library, and only provide
"stable-like" bug fix support until integrated projects are moved over to
the graduated library (although even that is up for discussion). After all
i
In preparing to fail builds with log errors I have been trying to make
things easier for projects by maintaining a whitelist. But these bugs in
ceilometer are coming in so fast that I can't keep up. So I am just
putting ".*" in the white list for any cases I find before gate failing
is turned
So, as I mention in the branch, what about deployments that haven't
transitioned to the library but would like to cherry pick this feature?
"after it starts moving into a library" can leave a very big gap when the
functionality isn't available to users.
-S
Folks, I understand that the review latency can be too long. We just
added two core reviewers and I am sure we can do better still. But
please, if you feel you must ping some one by name for a review, do so
in #openstack-qa rather than pinging on a private channel. That way
other people might s
On Fri, Nov 29, 2013 at 2:14 PM, Sandy Walsh wrote:
> So, as I mention in the branch, what about deployments that haven't
> transitioned to the library but would like to cherry pick this feature?
>
> "after it starts moving into a library" can leave a very big gap when the
> functionality isn't av
Hi Arvind
I have added my two-penneth to the latest version.
I look forward to your comments
regards
David
On 26/11/2013 23:07, Tiwari, Arvind wrote:
> Hi David,
>
> Thanks for your time and valuable comments. I have replied to your comments
> and try to explain why I am advocating to this
Hi,
We're currently running Grizzly (going to Havana soon) and we're running
into an issue where if the active controller is ungracefully killed then
nova-compute on the compute node doesn't properly connect to the new
rabbitmq server on the newly-active controller node.
I saw a bugfix in Fo
FYI, I pushed code review for the blueprint. The patch is missing unitest
and tempest. It's only submitted for discussion.
The patch implements two-step commit process similar to ML2, but it's not
intended to solve all race conditions. Another thing I think worth
discussing is how to work with age
On Nov 29, 02:22:17 PM (Friday), Chris Friesen wrote:
> We're currently running Grizzly (going to Havana soon) and we're
> running into an issue where if the active controller is ungracefully
> killed then nova-compute on the compute node doesn't properly
> connect to the new rabbitmq server on the
On 11/29/2013 06:37 PM, David Koo wrote:
On Nov 29, 02:22:17 PM (Friday), Chris Friesen wrote:
We're currently running Grizzly (going to Havana soon) and we're
running into an issue where if the active controller is ungracefully
killed then nova-compute on the compute node doesn't properly
conne
38 matches
Mail list logo