Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 mike.tutkowski@solidfire.com does not designate 209.85.214.179 as permitted
 sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACOnxChHWAL2+9epGT5RsuCDk+dneN+Uik2A=9Kk6Y2_9KGHuw@mail.gmail.com>
References: 
 <CACOnxChG6YXaUqc6tHNdFCwRK0rNw65TOd=YCeTwri4q=DtKQA@mail.gmail.com>
	<CALFpzo4V7ULARkTWj5P4Fw+DRCAd2HJGEft4Pzu6kRP7k47zMg@mail.gmail.com>
	<CACOnxCjrmL+vjYO9-eW6BUzDEce6E_FyMJRx7ACRniC2NqPkqQ@mail.gmail.com>
	<F95EC5DFF06AE04FA54C508ED869D0D2B599A7@agcex01.CORP.ISWEST.NET>
	<CACOnxCidqv3SOfwY-WM7EU-yq0_1F8OGd0VYs23G_-uPQ0epyA@mail.gmail.com>
	<CACOnxChHWAL2+9epGT5RsuCDk+dneN+Uik2A=9Kk6Y2_9KGHuw@mail.gmail.com>
Date: Tue, 22 Jan 2013 13:43:02 -0700
Message-ID: 
 <CACOnxCjOcET2r2cEaib0YY+dCgA8dJJnCGMYGFO6jrQq02MS4g@mail.gmail.com>
Subject: Re: CloudStack and Networking Question
From: Mike Tutkowski <mike.tutkowski@solidfire.com>
To: cloudstack-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff1c630c0ff0004d3e69f89

--e89a8ff1c630c0ff0004d3e69f89
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

So, it looks like DevCloud just uses NAT with port forwarding.

I'm not sure how I could use DevCloud and leverage iSCSI storage on my
company's LAN.

That was the main reason I had switched over to trying to build up a
CloudStack environment from scratch (in part, also, so I could see first
hand how it's done).


On Tue, Jan 22, 2013 at 1:28 PM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:

> Just heard back from a friend of mine.  He said he had Windows as his hos=
t
> OS, was running Ubuntu in a VM under VirtualBox and had the same issue as=
 I
> had (NAT worked; bridged didn't).
>
>
> On Tue, Jan 22, 2013 at 1:24 PM, Mike Tutkowski <
> mike.tutkowski@solidfire.com> wrote:
>
>> OK, thanks - I haven't gotten around to installing any agent software on
>> a host.  I'm just at the part where I was installing the MS on my OS in =
a
>> VM.
>>
>>
>> On Tue, Jan 22, 2013 at 1:22 PM, Clayton Weise <cweise@iswest.net> wrote=
:
>>
>>> The agent is what runs on KVM hosts to carry out requests from the
>>> management server(s).  The management server is the cloud-management
>>> service which oversees all the stuff CloudStack does.
>>>
>>> -----Original Message-----
>>> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
>>> Sent: Tuesday, January 22, 2013 12:17 PM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: Re: CloudStack and Networking Question
>>>
>>> Pranav =3D Yeah, good idea...I hooked my MacBook up via cable to the
>>> network
>>> and disabled the wireless, but it didn't work. :( I did get an IP addre=
ss
>>> and could access web sites on the Internet, but Tomcat was not running.
>>>
>>> Marcus =3D What is the difference between the Agent and the Management
>>> Server?  I followed the instructions here:
>>>
>>>
>>> http://incubator.apache.org/cloudstack/docs/en-US/Apache_CloudStack/4.0=
.0-incubating/html/Installation_Guide/management-server-install-flow.html
>>>
>>> In NAT mode, I usually get 10.0.2.15 as my IP address (no access from m=
y
>>> Mac).
>>> In bridged mode, as expected, I get an IP address on my company's LAN.
>>>
>>> I do have the source code in my Mac OX X environment, so maybe that is
>>> the
>>> route I will have to take.
>>>
>>> As an oddity on top of this all, if I run Tomcat 6 manually using the
>>> tomcat6 script in /etc/init.d/, Tomcat works.  I can hit
>>> http://localhost:8080, but it doesn't know about
>>> http://localhost:8080/client/
>>>
>>>
>>> On Tue, Jan 22, 2013 at 11:59 AM, Marcus Sorensen <shadowsor@gmail.com
>>> >wrote:
>>>
>>> > Mike, are you just trying to run the management server, not the agent=
,
>>> in a
>>> > VM? If you are trying to run the whole thing, it will fail with
>>> virtualbox
>>> > because cloudstack verifies that there is hardware support for
>>> > virtualization before starting the agent. This is not related to your
>>> issue
>>> > now, but you may run into it. If you want to run the agent and VMs
>>> inside
>>> > this VM, you will need to use VMware fusion and enable the nested
>>> > virtualization.
>>> >
>>> > Aside from that, check your network in the Ubuntu box and see what
>>> you're
>>> > getting in each mode. In NAT mode with virtualbox, you'll have no
>>> access to
>>> > the VM from your Mac, because your mac has no IP inside the NAT. This
>>> is
>>> > why devcloud uses both NAT and host-only.
>>> >
>>> > But it sounds like your issue is deeper because you cannot even get
>>> > cloud-management to start. In the past, if I have seen no errors in t=
he
>>> > log, but no success, I have edited the startup script to print out th=
e
>>> > actual command being run to start the management server (with class
>>> paths
>>> > and all), and then run it manually, perhaps adding a debug flag. That
>>> > usually gives me the error.
>>> >
>>> > As an alternative, you can pull the source code, build it, and do the
>>> > 'jetty:run' per devcloud instructions, and that should print debug
>>> code to
>>> > your screen. It could at least tell you why the management server won=
't
>>> > start, even if you don't want to install from master. That will requi=
re
>>> > cleaning out the database though, and then setting up the database
>>> again
>>> > when going back to 4.0.
>>> >
>>> > mvn -P developer,systemvm clean install
>>> >
>>> > mvn -P developer -pl developer,tools/devcloud -Ddeploydb
>>> >
>>> > mvn -pl :cloud-client-ui jetty:run
>>> >
>>> >
>>> > On Tue, Jan 22, 2013 at 11:42 AM, Mike Tutkowski <
>>> > mike.tutkowski@solidfire.com> wrote:
>>> >
>>> > > Hi,
>>> > >
>>> > > I'm running CloudStack on Ubuntu 12.04.1 in a VirtualBox VM.
>>> > >
>>> > > When I run it in NAT mode, it works (I can bring up the web page to
>>> log
>>> > in
>>> > > and my login works).
>>> > >
>>> > > In any other networking mode (bridged, internal, host only), it doe=
s
>>> not
>>> > > work (Tomcat is not running and I cannot get it to run (even though
>>> > there's
>>> > > no obvious error message) by running the cloud-management script).
>>> > >
>>> > > My host OS is Mac OS X and I am connected to my company's network
>>> over
>>> > > Mac's wireless network (AirPort).
>>> > >
>>> > > I have tried to use VMware instead of VirtualBox and come across th=
e
>>> same
>>> > > problem.
>>> > >
>>> > > Can anyone think of some reason this might be happening?  Does anyo=
ne
>>> > else
>>> > > develop CloudStack on Mac OS X using virtual machines?
>>> > >
>>> > > Thanks!
>>> > >
>>> > > --
>>> > > *Mike Tutkowski*
>>> > > *Senior CloudStack Developer, SolidFire Inc.*
>>> > > e: mike.tutkowski@solidfire.com
>>> > > o: 303.746.7302
>>> > > Advancing the way the world uses the
>>> > > cloud<http://solidfire.com/solution/overview/?video=3Dplay>
>>> > > *(tm)*
>>> > >
>>> >
>>>
>>>
>>>
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidFire Inc.*
>>> e: mike.tutkowski@solidfire.com
>>> o: 303.746.7302
>>> Advancing the way the world uses the
>>> cloud<http://solidfire.com/solution/overview/?video=3Dplay>
>>> *(tm)*
>>>
>>
>>
>>
>> --
>> *Mike Tutkowski*
>>  *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkowski@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the cloud<http://solidfire.com/solution=
/overview/?video=3Dplay>
>> *=99*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud<http://solidfire.com/solution/=
overview/?video=3Dplay>
> *=99*
>


--=20
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=3Dplay>
*=99*

--e89a8ff1c630c0ff0004d3e69f89--