Ryan, thank you for your excellent and detailed comments about problems
you encountered during the upgrade process. This is precisely the kind
of constructive feedback that is needed and desired.
Someone mentioned automated testing of upgrade paths. This is exactly
what needs to happen. Hopefully
Il giorno 27/ago/2012, alle ore 19:12, Vishvananda Ishaya
vishvana...@gmail.com ha scritto:
a snapshot and an image are the same. The only difference is a piece of
metadata saying what instance the snapshot came from.
Correct, but if one fails and the other not, the api call done by the
Hi-
When I'm logging into Horizon of Openstack Essex release,
I'm getting this error in the keystone log file...
(root): 2012-08-29 12:45:50,030 ERROR (IntegrityError) (1062, Duplicate
entry '' for key 'PRIMARY') 'INSERT INTO token (id, expires, extra) VALUES
(%s, %s, %s)'
I am using a mysql database.
I tried yesterday to re-install all nova services (just to identify the
source of the problem). So, I noticed that nova-compute is the failed
service. It does not restart when I set the libvirt_type to xen at the
nova-compute.conf file. Actually I am using an Ubuntu
For everybody's information. The patch for the essex release can be
downloaded here https://bugs.launchpad.net/nova/+bug/1040255/comments/7
On Tue, Aug 28, 2012 at 3:17 AM, Sam Su susltd...@gmail.com wrote:
Hi,
Thank you so much for your help.
I replaced the file
Hi
Now my network seting in nova.conf
network_manager=nova.network.manager.FlatDHCPManager
public_interface=eth0
flat_interface=eth1
flat_network_bridge=br100
how to setting eth1, as I know the eth1 no need setting IP address. some
document say need set eth1 to promisc, (
Hi Joe,
OK, this is clear to me, but I more think about this scenario: each keystone
has its own storage and the keystones are interconnected and replicating the
information on keystone layer - so for example one keystone can be connected
to LDAP another to DB or KVS etc.
Thanks a lot for your
You're looking to provide data redundancy across keystone instances with
varying backend implementations... what's your use case? How would you
orchestrate the synchronization and failover, if any? What's the purpose of
each backend in such a deployment?
-Dolph
On Wed, Aug 29, 2012 at 3:50 AM,
I think its great that we're having this discussion.
In the hope that its informative, I'd like to give some info on issues
we're looking at when moving our Glance deployment to Folsom. A lot of
this is in common with Ryan, but there are a couple of twists due to our
goals of maximization of
The HPCS portal does this for you via the Nova API when the account is created
– we haven’t implemented it as a specific Nova feature.
From: openstack-bounces+philip.day=hp@lists.launchpad.net
[mailto:openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf Of
Shake Chen
Sent: 24
While I don't know the root cause here, I did want to rule out that Glance
error as the cause. The code logging that line looks like this:
def process_response(self, resp):
try:
request_id = resp.request.context.request_id
except AttributeError:
Can you share the sequence of commands you used during the install process?
On Aug 29, 2012, at 3:18 AM, Trinath Somanchi wrote:
Hi-
I have installed Openstack Folsom-3 Glance for my testing and found this
error while db sync.
Jay Pipes jaypi...@gmail.com writes:
Someone mentioned automated testing of upgrade paths. This is exactly
what needs to happen. Hopefully the Tempest folks can work with the CI
team in the G timeframe to incorporate upgrade path testing for the
OpenStack components.
I am strongly in favor
Hi Dolph,
Well, I don't have such use case (this just came to my mind), but yes, it's
with data redundancy, etc. I think about synchronization at Keystone level ...
the failover is the problem. As I wrote, I'm curious if this is possible.
Thanks for your answer.
Pat
On Wed, 29 Aug 2012
Thank you so much for you guys help.
I will do these later.
Actually this problem can be reproduced in my Essex environment, and I have
no idea about how to figure out why it happened, but I'd like to try it. It
is highly appreciated if someone can give me some suggestions.
Thanks,
Sam
On Tue,
Hi all -
Here's a weekly report from docs land. Thanks for reading!
tl;dr - Summarizes the doc activities and related news of the past week.
1. In review and merged this past week:
Quantum API guide v2.0 now merged, build job created, still needs to
be linked from API landing page
CLI guide now
It looks like the primary key is not being inserted. It looks like you are
trying to run an essex release of keystone against a folsom keystone db. The
folsom db has a primary key of id_hash so the insert is failing.
Vish
On Aug 29, 2012, at 12:38 AM, Dolph Mathews dolph.math...@gmail.com
Hi all,
What's your experience with multinic?
If I want to have multiple interfaces per instance connected to
separate physical interfaces what would be the best option?
I've found these flags in the documentation:
--bridge=bridge
--bridge_interface=bridge interface
But for some reason it's
Hi-
Oh. got the difference, thanks for the reply
How to kow wat are all the differences that are in place form Essex to
Folsom-3 in Openstack. Can you share me a document/link/details on this
area.
Thanking you for the help.
--
TNS
On Wed, Aug 29, 2012 at 9:52 PM, Vishvananda Ishaya
Hi-
here are my steps:
[1] I have just downloaded the tar.gz file of glance
[2] untar and run the following commands, python setup.py build , python
setup.py install
[3] create the galnce db in mysql manually.
[4] previously done with keystone work as specified in the ESSESX release,
since I dont
I think a new release should contains details of how to do the upgrade
(rather than discovering as we try it)
I should aim that the deliverables for each of the projects in a new version
includes in the release notes:
A. dependencies (i.e. does glance folsom need to talk to horizon folsom or
Hi Naveen,
That is almost correct. You can associate a provider network (either a
physical network or a vlan) with a Quantum network. The association is at
the network level, not the subnet level.
As the 'provider networks' is an extension in quantum, there is no direct
CLI option available.
Perhaps we should also have a CHANGELOG file to explain the major
features/changes...
Perhaps a 'MIGRATION' file as well that explains how to migrate from
version - 1?
On 8/29/12 10:15 AM, Tim Bell tim.b...@cern.ch wrote:
I think a new release should contains details of how to do the upgrade
One other comment: sometimes people use the term provider network
to mean two things:
1) a quantum network that maps directly to an existing physical or
vlan network in the provider's infrastructure.
2) a shared network that all tenants have access to (e.g., to reach
the Internet).
In Quantum,
Hi Aaron,
Thanks as usual for the reply.
I mostly root caused the horizon error last night and filed a bug that
ultimately was resolved as duplicate to the following:
https://bugs.launchpad.net/horizon/+bug/1040956, which I am sure the horizon
people are all over now.
Until that bug is fix,
Thanks Salvatore and Dan. I was asking for #1 below, as my use-case was to map
a quantum network to an existing provider vlan. #2 is also quite useful to
know.
Naveen
-Original Message-
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Wednesday, August 29, 2012 11:28 AM
To:
Hi,
Thank you all for you suggestions.
After updated the table fixed_ips and floating_ips, this problem was
eventually fixed.
I finally figure out how to reproduce this problem:
If an instance associated with a floating IP is terminated, the instance
can be successfully terminated, but the
Hi the list,
I had issues with nova-scheduler, but after upgrading ubuntu packages,
the problem have disapeared.
Now, I have another well know problem : on a multinode setup, I have a
connection refused when the instance tries to get metadata from nova-api :
2012-08-29 22:00:05,968 -
Try:
--metadata_host=94.xx.xx.50
--dmz_cidr=94.xx.xx.50/32
Vish
On Aug 29, 2012, at 3:14 PM, Ben ben@gmail.com wrote:
Hi the list,
I had issues with nova-scheduler, but after upgrading ubuntu packages, the
problem have disapeared.
Now, I have another well know problem : on a
Hi Vish,
Thanks for your fast answer.
I tried these options on all nodes, but it didn't seems to work
(connection refused again).
I have googled a bit more, and I saw I can load nova-api on each compute
nodes, with only the metadata service (--enabled_apis=metadata).
This setup works well and
On Wed, Aug 29, 2012 at 12:19 PM, Joshua Harlow harlo...@yahoo-inc.com wrote:
Perhaps we should also have a CHANGELOG file to explain the major
features/changes...
Perhaps a 'MIGRATION' file as well that explains how to migrate from
version - 1?
I think that this would be a great start.
In
Hello,
As we are observing that the current meeting time is not very convenient
for a few contributors, we would like to propose to change the date and
time to something that would suit a larger number. I propose that we do
this in a two phase process:
1/ Each project member that care should
On Aug 29, 2012, at 4:16 PM, Ben ben@gmail.com wrote:
And about nova.conf format, should I prefix options or not ?
no. The new format is without -- and -- will not work in folsom.
Vish
___
Mailing list: https://launchpad.net/~openstack
Post to
On 29/08/12 19:21 -0700, Nick Barcet wrote:
Hello,
As we are observing that the current meeting time is not very convenient
for a few contributors, we would like to propose to change the date and
time to something that would suit a larger number. I propose that we do
this in a two phase
Hi,
The metering project team holds a meeting in #openstack-meeting,
Thursdays at 1600 UTC
http://www.timeanddate.com/worldclock/fixedtime.html?hour=16min=0sec=0.
Everyone is welcome.
Agenda:
http://wiki.openstack.org/Meetings/MeteringAgenda
* Review last week's actions
- jaypipes to
Hi Swifters，
I use keystone for the authentication and authorization of swift. During
the benchmark test, I also encountered this kind of problems
https://bugs.launchpad.net/keystone/+bug/1020127.
I do some changes that moved the auth_toke and swift_auth middlewares into
swift and replace the
FYI
From: openstack-bounces+zhongyue.nah=intel@lists.launchpad.net
[mailto:openstack-bounces+zhongyue.nah=intel@lists.launchpad.net] On Behalf
Of Alex Yang
Sent: Thursday, August 30, 2012 11:46 AM
To: openstack@lists.launchpad.net
Subject: [Openstack] [OpenStack][Swift] How about move
Hi.
I made my first little patch:
https://review.openstack.org/#/c/12048/
which failed 3 times on
http://logs.openstack.org/12048/1/check/gate-tempest-devstack-vm/9570
which surely is not my issue. What can I do with this? Also, who should
I ask to review it and submit?
Thanks, J.H
--
38 matches
Mail list logo
