I guess that's not physical either... since ifConfig -a on the Ubuntu OS(where 
my VM resides) gave me different HWaddr (something like  5a:86:eb:95:1a:49).  
So, another question is whether I can get the physical NIC port MAC from 
Openstack Quantum? The plugin configured in my environment is OVS plugin.

Thanks,

YuLing

-----Original Message-----
From: Maru Newby [mailto:ma...@redhat.com] 
Sent: Tuesday, April 30, 2013 11:32 AM
To: C, Yuling
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] anyone has a sample quantum.conf file that configures 
a valid quantum.log file?


On Apr 30, 2013, at 11:21 AM, yulin...@dell.com wrote:

> Thanks very much Maru.
> 
> Another question...I'm playing around with Openstack Dashboard. What I can 
> see is that after I launch a VM, a few ports will be created. Port details 
> would also show the MAC address of the port(something like 
> fa:16:3e:97:1f:b7). Is this MAC address the physical MAC address of the port 
> on the NIC card? If not, what MAC address is it?

It is likely the mac of a virtual nic (quantum port), though the specifics 
would depend on which Quantum plugin is configured.



> Thanks,
> 
> YuLing
> 
> -----Original Message-----
> From: Maru Newby [mailto:ma...@redhat.com] 
> Sent: Tuesday, April 30, 2013 2:03 AM
> To: C, Yuling
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] anyone has a sample quantum.conf file that 
> configures a valid quantum.log file?
> 
> On Apr 29, 2013, at 6:03 PM, yulin...@dell.com wrote:
> 
>> 
>> 
>> Hi,
>> 
>> I'm new to Quantum and trying to set up an openstack quantum environment.
>> 
>> I installed a single node environment using DevStack(on a VM) successfully. 
>> I noticed that by default there is no log files for quantum. I tried to 
>> enable the quantum logging using quantum.conf. However, I haven't been lucky 
>> enough to get it work yet. Just wondering if anyone can share a working 
>> sample of quantum.conf that enables logging to a log file?
> 
> The default devstack configuration is to have the processes log to a screen 
> session.  If file output is desired, add the following to your localrc
> 
> SCREEN_LOGDIR=$DEST/logs/screen
> 
> This ensures that log output is also captured to disk - a file per service in 
> the specified output directory.
> 
> Thanks,
> 
> 
> Maru
> 
> 
>> 
>> Thanks,
>> 
>> YuLing
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
> 


_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to