/site-packages/keystone-2012.1-py2.6.egg/keystone/middleware/ec2_token.py,
line 35, in module
(nova): TRACE: flags.DEFINE_string('keystone_ec2_url',
(nova): TRACE: AttributeError: 'module' object has no attribute 'DEFINE_string'
--
Dr. Dong-In David Kang
Computer Scientist
nbd6 nvram
ram10 ram4 rootsg1 sg9 tty tty15 tty22 tty3 tty37
tty44 tty51 tty59 tty9 usbmon2 vcs1 vcsa2 VolGroup
Thanks,
David
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
Sure,
It is done.
It is reported as
OpenStack Compute (nova) Bugs Bug #1009701
Thanks,
David
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
- Original Message -
Hi,
Can you please open up a bug in Launchpad please?
thanks
chuck
On Tue, 5 Jun
(instead of db access) to access
those information from multiple bare-metal nova-compute nodes.
Thanks,
David
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
- Original Message -
Can you elaborate what is the purpose of this database?
If we compare it to KVM
Hi Vish,
Is this discussion for long-term goal or for this Folsom release?
We still believe that bare-metal database is needed
because there is not an automated way how bare-metal nodes report their
capabilities
to their bare-metal nova-compute node.
Thanks,
David
I am interested
-In David Kang
Computer Scientist
USC/ISI
- Original Message -
This was an immediate goal, the bare-metal nova-compute node could
keep an internal database, but report capabilities through nova in the
common way with the changes below. Then the scheduler wouldn't need
access to the bare
. Then the scheduler wouldn't need
access to the bare metal database at all.
On Aug 15, 2012, at 4:23 PM, David Kang dk...@isi.edu wrote:
Hi Vish,
Is this discussion for long-term goal or for this Folsom release?
We still believe that bare-metal database is needed
because
believe.
Thanks,
David
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
- Original Message -
Hi,
Could someone give a practical overview of how configuring and using
the instance type extra specs extension capability introduced in
Folsom?
If how
in self.last_capabilities:
+ name = capability_item.get('service_name', self.service_name)
+ host = capability_item.get('host', self.host)
+ self.scheduler_rpcapi.update_service_capabilities(context,
+ name, host, capability_item)
On Aug 21, 2012, at 1:28 PM, David Kang dk...@isi.edu wrote:
Hi Vish
could be have a many-to-one relationship with services.
You would just have to use a little more than hostname. Perhaps
(hostname, hypervisor_hostname) could be used to update the entry?
Vish
On Aug 24, 2012, at 11:23 AM, David Kang dk...@isi.edu wrote:
Vish,
I've tested your
= capability_item.get('service_name', self.service_name)
+ host = capability_item.get('host', self.host)
+ self.scheduler_rpcapi.update_service_capabilities(context,
+ name, host, capability_item)
On Aug 21, 2012, at 1:28 PM, David Kang dk...@isi.edu wrote:
Hi Vish,
We
machines in
the 'service' table.
In addition to that I think you suggest augmenting 'host' field in the
'service' table,
such that 'host' field can be used for RPC.
(I don't think the current 'host' field can be used for that purpose now.)
David
- Original Message -
David Kang dk
Hello,
We will use different webex host today because of some technical problem.
Sorry for that.
David
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
- Original Message -
I am guessing your intent is to determine the maximum available
bandwidth
While setting up webex, please call
1-866-528-2256; code: 3289628
for the audio conference.
Thanks,
David
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
- Original Message -
Hello,
We will use different webex host today because of some technical
Webex,
https://usc-isi.webex.com/mw0306ld/mywebex/default.do?siteurl=usc-isi
password: dodcs
David
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
- Original Message -
While setting up webex, please call
1-866-528-2256; code: 3289628
for the audio
/GrizzlyHPC)
Hope to see you there.
Thanks,
David
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net
,
David
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https
and
to manage the discussion.
We can discuss this issue again among the people who signed up the new mailing
list.
Thanks,
David
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
- Original Message -
David Kang wrote:
Hello all,
An openstack mailing list
Victor,
You raised a very good point.
If you want to use any existing flag, what Razique said is OK.
But if you want to add new key value pairs, I don't think the current
nova-compute can do that.
Especially if you are using the currnent nova/virt/libvirt as compute driver,
you cannot.
In
/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
--
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
___
Mailing list: https
between DMZ network and
non-DMZ network within itself by default.
Have anybody configured Quantum for this case?
Any help will be appreciated.
We are using Quantum linuxbridge-agent.
Thanks,
David
--
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
router for your dmz hosts then
traffic in/out of that network should route our to your physical
infrastructure which will go through your router to do filtering.
Thanks,
Aaron
On Wed, Apr 3, 2013 at 8:26 AM, David Kang dk...@isi.edu wrote:
Hi,
We are trying to set up
quantum router-gateway-set non-DMZ-router non-DMZ
On Thu, Apr 4, 2013 at 10:51 AM, David Kang dk...@isi.edu wrote:
Hi Aron,
Thank you for your reply.
We deploy one (quantum) subnet as a DMZ network and the other
(quantum) subnet
as a non-DMZ network.
They are routed
think it should work as it is because 10.12.183.1 is lower than
10.12.83.1 in
the routing table.
What could be wrong?
I will appreciate any help.
Thanks,
David
--
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
the Quantum network work well
than just commenting them out?
I'll appreciate your help.
David
--
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack
: David Kang dk...@isi.edu
To: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
openstack@lists.launchpad.net
Sent: Tuesday, July 23, 2013 7:22 PM
Subject: [Openstack] [Quantum/Neutron] VM cannot get IP address from
DHCP server
Hi,
We are running OpenStack Folsom on CentOS
We use CentOS 6.4, which does not support network namespace.
So ip netns .. fails.
Thanks,
David
- Original Message -
that will not show the rules for the instance. try this
ip netns exec yourrouter-uuid iptables -nxvL
On Jul 23, 2013, at 09:59 , David Kang dk...@isi.edu wrote
,
Gabriel
From: David Kang dk...@isi.edu
To: Staicu Gabriel gabriel_sta...@yahoo.com
Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
openstack@lists.launchpad.net
Sent: Tuesday, July 23, 2013 7:59 PM
Subject: Re: [Openstack] [Quantum/Neutron] VM cannot get IP address
,
Gabriel
From: David Kang dk...@isi.edu
To: Staicu Gabriel gabriel_sta...@yahoo.com
Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
openstack@lists.launchpad.net
Sent: Tuesday, July 23, 2013 7:59 PM
Subject: Re: [Openstack] [Quantum/Neutron] VM cannot get IP
Thank you, Brian.
David
- Original Message -
On 07/23/2013 12:22 PM, David Kang wrote:
Hi,
We are running OpenStack Folsom on CentOS 6.4.
Quantum-linuxbridge-agent is used.
By default, the Quantum node has the following entries in its
/etc/sysconfig/iptables file
iptables -t filter -I FORWARD -i qg-+ -o qr-+ -j ACCEPT
iptables -t filter -I FORWARD -i qr-+ -o qr-+ -j ACCEPT
But it doesn't work for me.
Any suggestion?
Thanks,
David
- Original Message -
On 07/23/2013 12:22 PM, David Kang wrote:
Hi,
We are running OpenStack Folsom
size 65535
bytes
13:48:46.892785 IP 192.168.3.3 10.12.182.13: ICMP echo request, id 46605, seq
1855, length 64
13:48:46.892825 IP 192.168.3.2 192.168.3.3: ICMP host 10.12.182.13
unreachable - admin prohibited, length 92
- Original Message -
On 07/23/2013 11:41 PM, David Kang wrote
Thanks, Brian.
My answers are put in your email with --.
David
- Original Message -
On 07/24/2013 10:42 AM, David Kang wrote:
If I remove the following REJECT rules, it works perfectly.
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject
own, as it
looks like
it's your iptables config causing it, you just need to get the correct
rules in
there.
-Brian
On 07/24/2013 11:34 AM, David Kang wrote:
Thanks, Brian.
My answers are put in your email with --.
David
- Original Message -
On 07/24/2013 10:42 AM
- Original Message -
Hi,
So I was the developer who added support for LXC support initially, I
have some comments in line
On Tue, 6 Dec 2011 12:04:53 -0800 (PST)
Dong-In David Kang dk...@isi.edu wrote:
- Original Message -
On Mon, Dec 05, 2011 at 09:07:06PM
How about adding the following two flags in nova.conf file?
We are running flat dhcp without problem.
You need to customize the values of the flags.
--flat_network_dhcp_start=10.99.1.2
--flat_interface=eth0
David.
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
On Thu, Dec 15, 2011 at 2:29 PM, Dong-In David Kang dk...@isi.edu
wrote:
I'm trying to make novaclient work with keystone.
It looks like authentication is working, but actual interaction
between novaclient and nova does not work.
Here is what I get (with added debugging messages I
On Thu, Dec 15, 2011 at 2:29 PM, Dong-In David Kang dk...@isi.edu
wrote:
I'm trying to make novaclient work with keystone.
It looks like authentication is working, but actual interaction
between novaclient and nova does not work.
Here is what I get (with added debugging
On Fri, Dec 16, 2011 at 10:46 AM, Dong-In David Kang dk...@isi.edu
wrote:
The server has either erred or is incapable of performing the
requested operation. (HTTP 500)
It was due to the version of webob.
The installed version was 1.2b.
After reverting it to 1.1.1, it works fine
39 matches
Mail list logo