Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of
 rayees.namathponnan@citrix.com designates 66.165.176.89 as permitted sender)
From: Rayees Namathponnan <rayees.namathponnan@citrix.com>
To: Chip Childers <chip.childers@sungard.com>, Pradeep Soundararajan
	<pradeep.soundararajan@citrix.com>
CC: Wido den Hollander <wido@widodh.nl>, "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Wed, 6 Feb 2013 16:22:46 -0800
Subject: RE: [DISCUSS] Packaging in 4.1
Thread-Topic: [DISCUSS] Packaging in 4.1
Thread-Index: Ac4EijQtdQqnRUOjQ6mzahRtD3j33gAOXqIw
Message-ID: 
 <99BD5B5740E6DA41AD584B49E414BD90012DB2B940EB@SJCPMAILBOX01.citrite.net>
References: 
 <CAKprHVZhoA6y3z+AWghSwtH1im32+gVHJZOQ-iRSm3+r4-eb1Q@mail.gmail.com>
 <CANLSSBXffHZv06dkRcQ3SM9h28zR+h9NXT7Gepb2G1n98B33Sw@mail.gmail.com>
 <7914B38A4445B34AA16EB9F1352942F1012F15861558@SJCPMAILBOX01.citrite.net>
 <510F8E64.70906@widodh.nl>
 <CANc7MVxyz_7g0a+h5QsiX4TFJUDKGkq16QFJwrBFTZ1w-5kYTQ@mail.gmail.com>
 <51116563.6000906@widodh.nl>
 <35F04D4C394874409D9BE4BF45AC5EA9010F3AF6FF98@BANPMAILBOX01.citrite.net>
 <20130206155734.GM88803@USLT-205755.sungardas.corp>
 <51128575.4060607@widodh.nl>
 <35F04D4C394874409D9BE4BF45AC5EA9010F3AF70078@BANPMAILBOX01.citrite.net>
 <20130206165034.GC93832@USLT-205755.sungardas.corp>
In-Reply-To: <20130206165034.GC93832@USLT-205755.sungardas.corp>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

As per Pradeep's suggestion I modified package.sh,  (updated  "cloud" to "c=
loudstack" in .../centos63/package.sh)

I am able to create new packages  with above changes in Centos6.3,  and als=
o able to install MS; but "cloudstack-setup-management" failed with below e=
rror=20

[root@auto_ms1 CloudStack-non-OSS-20-rhel6.3]# cloudstack-setup-management
Starting to configure CloudStack Management Server:
Configure sudoers ...         [OK]
Configure Firewall ...        [OK]
Configure CloudStack Management Server ...[Failed]
Cannot find /etc/cloud/management/server-nonssl.xml or /etc/cloud/managemen=
t/tomcat6-nonssl.conf, https enables failed
Try to restore your system:
Restore sudoers ...           [OK]
Restore Firewall ...          [OK]
Restore CloudStack Management Server ...[OK]
[root@auto_ms1 CloudStack-non-OSS-20-rhel6.3]#


"cloudstack-setup-management "  looking for the old path /etc/cloud/managem=
ent, instead of /etc/cloudstack/management


Hi Wido,

You will be having fixes for this ? is there any workaround for this ?

Regards,
Rayees

-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]=20
Sent: Wednesday, February 06, 2013 8:51 AM
To: Pradeep Soundararajan
Cc: Wido den Hollander; cloudstack-dev@incubator.apache.org
Subject: Re: [DISCUSS] Packaging in 4.1

On Wed, Feb 06, 2013 at 10:05:00PM +0530, Pradeep Soundararajan wrote:
> Wido, how are we planning to setup the install for this new packaging con=
cept?
>=20

Well, first, Apache CloudStack only releases source code.

But Wido is kind enough to also host RPM / DEB package repos for users to t=
ake advantage of.  Our install guide explains how to build from source, as =
well as how to use Wido's repos.

This was all true for 4.0.0-incubating, and I think it still holds true for=
 all future releases.

> Thanks,
> Pradeep S
>=20
>=20
> -----Original Message-----
> From: Wido den Hollander [mailto:wido@widodh.nl]
> Sent: Wednesday, February 06, 2013 10:02 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Packaging in 4.1
>=20
>=20
>=20
> On 02/06/2013 04:57 PM, Chip Childers wrote:
> > On Wed, Feb 06, 2013 at 03:30:04PM +0530, Pradeep Soundararajan wrote:
> >> Thanks Hugo, Wido and Noa for bringing this to some closure :)
> >>
> >> I am able to package rpm using "packaging/centos63/package.sh" after s=
ome modification in the package.sh script since cloud.spec is looking for '=
cloudstack' Name.
> >>
> >> -------------------------------------------------------------------
> >> --
> >> --- -mkdir -p $RPMDIR/SOURCES/cloud-$VERSION
> >> +mkdir -p $RPMDIR/SOURCES/cloudstack-$VERSION
> >>
> >>
> >> -(cd ../../; tar -c --exclude .git --exclude dist  .  | tar -C=20
> >> $RPMDIR/SOURCES/cloud-$VERSION -x ) -(cd $RPMDIR/SOURCES/; tar -czf=20
> >> cloud-$VERSION.tgz cloud-$VERSION)
> >> +(cd ../../; tar -c --exclude .git --exclude dist  .  | tar -C=20
> >> +$RPMDIR/SOURCES/cloudstack-$VERSION -x ) (cd $RPMDIR/SOURCES/; tar=20
> >> +-czf cloudstack-$VERSION.tgz cloudstack-$VERSION)
> >> -------------------------------------------------------------------
> >> --
> >> ----
> >>
> >> Packaging went fine after the above modification but I have observed s=
ome issues while installing the package.  I believe you have changed the in=
stallation path from */cloud/* to */cloudstack/* and also observed you have=
 changed all the rpm names from cloud* to cloudstack*.  If that is a situat=
ion then I feel we cannot upgrade from 4.0 since they were pointing to diff=
erent rpm names and they were loaded in a different location.  I feel,  thi=
s would raise lot of compatibility issues here and there.
> >>
> >> Noticed you have changed cloud-client to cloudstack-management. I feel=
, we have to modify install.sh script accordingly in order to satisfy all t=
he changed conditions.
> >
> > Haven't we removed install.sh completely?
>=20
> wido@wido-laptop:~/repos/cloudstack$ find -name 'install.sh'
> wido@wido-laptop:~/repos/cloudstack$
>=20
> Says enough I think? :)
>=20
> Wido
>=20
> >
> >>
> >> Time being shall we keep all the internals intact with the same name c=
loud instead of cloudstack?
> >>
> >> Please let us know if any one see any other issues.
> >>
> >> Thanks,
> >> Pradeep S
>=20