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 <shadow...@gmail.com>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 tripping up on multiple physical networks (I only want them on
> physical eth0), and I need to be able to set traffic labels to match
> physical networks to bridges.
>
>
> On Fri, Jan 11, 2013 at 10:41 AM, Marcus Sorensen <shadow...@gmail.com>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.apache.org/confluence/display/CLOUDSTACK/Testing+with+Python 
>> under
>> 'how do I generate it', if I copy that python script into devcloud and run
>> it, I end up with the following broken globalConfig:
>>
>>     "globalConfig": [
>>         {
>>             "name": "name",
>>             "value": "value"
>>         },
>>         {
>>             "name": "name",
>>             "value": "value"
>>         }
>>     ],
>>
>> If I delete that then the 431 goes away.
>>
>> Also, I don't see a way to edit the traffic labels on the advanced
>> network stuff in marvin, that would be extremely useful.
>>
>> Lastly, It seems that if I set a vlan range for a zone, marvin attempts
>> to set that vlan range for every physical network defined for the zone. So
>> the first one succeeds, the second one fails. The vlan property should be
>> moved up to be a member of the physical network as far as marvin is
>> concerned. We're in the process of making changes that allow you to use the
>> same vlan numbers on different physical networks anyway, since it's
>> possible that you can have completely separate infrastructure on each nic.
>>
>>
>> On Fri, Jan 11, 2013 at 10:09 AM, John Kinsella <j...@stratosec.co> wrote:
>>
>>> very cool - hoping I can get a chance to test this out and give some
>>> feedback within the next week or so.  Thanks!
>>>
>>> On Jan 10, 2013, at 10:53 AM, Marcus Sorensen <shadow...@gmail.com>
>>> wrote:
>>>
>>> > Guys,
>>> >  I'm writing up basic instructions on how to run a devcloud-kvm virtual
>>> > machine, for KVM development. The setup is complete, but I've run into
>>> a
>>> > few things as far as configuration that I'd like some help on.
>>> >
>>> > 1) running services. In the past I've just built rpms and installed
>>> them in
>>> > the devcloud-kvm. Not only does this not work on master right now, but
>>> it
>>> > takes an extra 60 seconds. With devcloud we run "mvn -P
>>> developer,systemvm
>>> > clean install && mvn -pl :cloud-client-ui jetty:run", I'm assuming I'll
>>> > have to start the agent as well... or I guess my question is how that's
>>> > handled when a normal zone creation expects the agent to be installed
>>> on
>>> > the KVM host.
>>> >
>>> > 2) how to go about configuration. I'd like to have a marvin config that
>>> > does two physical networks and an advanced zone, but I wasn't able to
>>> get
>>> > anything but a 431 error when trying anything custom with a marvin cfg
>>> file
>>> > (both in the standard devcloud and here). I played with the sandbox
>>> example
>>> > at
>>> >
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Testing+with+Pythonas
>>> > well as trying to create my own cfg file, and both resulted in 431 when
>>> > connecting to the management server for configuration.
>>>
>>> Stratosec - Secure Infrastructure as a Service
>>> o: 415.315.9385
>>> @johnlkinsella
>>>
>>>
>>
>

Reply via email to