On Mon, Jan 14, 2013 at 08:25:51PM -0500, Marcus Sorensen wrote:
> I've now got a config for regular devcloud in
> tools/devcloud/devcloud-advanced.cfg, this works for me to deploy a fully
> working advanced network zone, except for the traffic labels. If I go in
> and manually fix the traffic labe
You can use tools/devcloud/devcloud-advanced.cfg and the normal devcloud2.
I haven't updated the image on the kvm one yet.
On Jan 14, 2013 7:27 PM, "prasanna" wrote:
> Hey Marcus, Is the latest devcloud-kvm image you shared via the wiki
> up to date? I'll try it out and see why traffic labels fa
Hey Marcus, Is the latest devcloud-kvm image you shared via the wiki
up to date? I'll try it out and see why traffic labels failed to
configure. Thanks,
On 15 January 2013 06:55, Marcus Sorensen wrote:
> I've now got a config for regular devcloud in
> tools/devcloud/devcloud-advanced.cfg, this w
I've now got a config for regular devcloud in
tools/devcloud/devcloud-advanced.cfg, this works for me to deploy a fully
working advanced network zone, except for the traffic labels. If I go in
and manually fix the traffic labels to be as shown in the config, then
restart management server/system vm
Thanks. I've tested the vlan stuff and it seems to work. Now I'm stuck on
the traffic labels. My config deploys but my traffic labels all show 'Use
default network'. My script generated the following:
{
"zones": [
{
"localstorageenabled": "true",
"name": "testzo
I've fixed the problem of the same vlan applied to all the physical
networks with CLOUDSTACK-968 [1]. The vlan attribute went back-and-forth
b/w zone and phy. network when the physical-network concept was
introduced. Looks like I failed to fix marvin then.
Also while fixing this I noticed our Zone
{
"zones": [
{
"localstorageenabled": "true",
"name": "testzone",
"guestcidraddress": "10.1.1.0/24",
"dns1": "8.8.8.8",
"vlan": "3900-3919",
"physical_networks": [
{
"broadcastdom
On Fri, Jan 11, 2013 at 12:50:45PM -0500, Marcus Sorensen wrote:
> I'm attaching the cfg file that I have so far. The goal is to run
> everything in the devcloud, with public traffic on the NAT xenbr1
> bridge, management, guest vlans on xenbr0. As mentioned, the 'vlan'
> setting under zone is trip
Marcus - Thanks for bringing these up:
On Fri, Jan 11, 2013 at 12:41:08PM -0500, Marcus Sorensen wrote:
> Let me verify that everything is working first :-)
>
> I've had a chance to play with some of the marvin stuff a bit, and am
> running into a few issues. Per the example on
> https://cwiki.ap
Oh, and this is with normal devcloud, I'm trying to get the configs working
and then once I get the agent start figured out on devcloud-kvm I'll tweak
the cfg to work for that.
On Fri, Jan 11, 2013 at 10:50 AM, Marcus Sorensen wrote:
> I'm attaching the cfg file that I have so far. The goal is to
I'm attaching the cfg file that I have so far. The goal is to run
everything in the devcloud, with public traffic on the NAT xenbr1 bridge,
management, guest vlans on xenbr0. As mentioned, the 'vlan' setting under
zone is tripping up on multiple physical networks (I only want them on
physical eth0)
Let me verify that everything is working first :-)
I've had a chance to play with some of the marvin stuff a bit, and am
running into a few issues. Per the example on
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Testing+with+Python
under
'how do I generate it', if I copy that python scri
12 matches
Mail list logo
