I'm confused here :(
Changes to micro_bosh.yml will affect my release deployment as well? I
thought micro_bosh.yml was used exclusively for provisioning (micro) bosh
and release deployment uses a separate yml (in case of sample wordpress,
wordpress.yml).

Nevertheless I put the kernel_id: aki-88aa75e1 (picked from this site<http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/UserProvidedkernels.html>
) change in micro_bosh.yml file and registered the stemcell (after changing
version number).System logs show that the instance does indeed boot
successfully. The compilation task, however continues to time out.

Please guide.
On Friday, August 3, 2012 12:12:18 PM UTC+5:30, Martin Englund wrote:

Ankit,

you can specify the aki you want in your micro_bosh.yml:

cloud:
properties:
stemcell:
kernel_id: aki-...

/M
On Thu, Aug 2, 2012 at 11:03 PM, Ankit wrote:
Thanks for the quick reply!

Is the release for the new AWS stemcell due soon? Also is there a work
around,( like previous version or any version of the stemcell that can get
things rolling) for me in the meanwhile?

On Friday, August 3, 2012 11:20:20 AM UTC+5:30, Martin Englund wrote:

For bosh-stemcell-0.5.1 you need the hd0 aki. Once we can release the
new
AWS stemcell the deployer can auto-select the aki (the information
needed is
available in the new stemcell)

/M

Sent from my iPhone

On Aug 2, 2012, at 22:23, Ankit wrote:

Hello,

I am using bosh-stemcell-aws.0.5.1.tgz and the AKI associated with the
AMI
when I upload the stemcell is aki- b4aa75dd.
The bosh deployer version is 0.4.0.

Thanks!
On Thursday, August 2, 2012 10:37:27 PM UTC+5:30, Martin Englund wrote:

Ankit,

I think you have specified the wrong AKI - which stemcell are you
using? And which version of the deployer?

cheers,
/Martin
On Thu, Aug 2, 2012 at 6:51 AM, Ankit wrote:
Hello,

I am trying to deploy a sample release on AWS backed micro bosh
instance
(following
https://github.com/drnic/bosh-getting-started/blob/master/create-a-bosh/creating-a-micro-bosh-from-stemcell.md
and
https://github.com/drnic/bosh-getting-started/blob/master/deploying-sample-release.md)
But when I try to deploy the release, the compilation tasks fail
after
waiting for 5 mins for the instance to come up. Similar to problem
resolved
in
https://groups.google.com/a/cloudfoundry.org/forum/#!topic/bosh-users/Oh0IiTLbQMI
I tweaked the stemcell manifest, but that did not solve the issue as
well :(

System logs from the aws instance show the following text,

Xen Minimal OS!
start_info: 0xce2000(VA)
nr_pages: 0x6a400
shared_inf: 0x901be000(MA)
pt_base: 0xce5000(VA)
nr_pt_frames: 0xb
mfn_list: 0x990000(VA)
mod_start: 0x0(VA)
mod_len: 0
flags: 0x0
cmd_line: root=/dev/sda ro 4
stack: 0x94f860-0x96f860
MM: Init
_text: 0x0(VA)
_etext: 0x5ffbd(VA)
_erodata: 0x78000(VA)
_edata: 0x80ae0(VA)
stack start: 0x94f860(VA)
_end: 0x98fe68(VA)
start_pfn: cf3
max_pfn: 6a400
Mapping memory range 0x1000000 - 0x6a400000
setting 0x0-0x78000 readonly
skipped 0x1000
MM: Initialise page allocator for
103e000(103e000)-6a400000(6a400000)
MM: done
Demand map pfns at 6a401000-206a401000.
Heap resides at 206a402000-406a402000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x6a401000.
Initialising scheduler
Thread "Idle": pointer: 0x206a402010, stack: 0x13b0000
Initialising xenbus
Thread "xenstore": pointer: 0x206a4027c0, stack: 0x13c0000
Dummy main: start_info=0x96f960
Thread "main": pointer: 0x206a402f70, stack: 0x13d0000
"main" "root=/dev/sda" "ro" "4"
vbd 2048 is hd0
******************* BLKFRONT for device/vbd/2048 **********


backend at /local/domain/0/backend/vbd/373/2048
Failed to read /local/domain/0/backend/vbd/373/2048/feature-barrier.
Failed to read
/local/domain/0/backend/vbd/373/2048/feature-flush-cache.
4194304 sectors of 512 bytes
**************************
vbd 2051 is hd1
******************* BLKFRONT for device/vbd/2051 **********


backend at /local/domain/0/backend/vbd/373/2051
Failed to read /local/domain/0/backend/vbd/373/2051/feature-barrier.
Failed to read
/local/domain/0/backend/vbd/373/2051/feature-flush-cache.
1835008 sectors of 512 bytes
**************************
vbd 2064 is hd2
******************* BLKFRONT for device/vbd/2064 **********


backend at /local/domain/0/backend/vbd/373/2064
Failed to read /local/domain/0/backend/vbd/373/2064/feature-barrier.
Failed to read
/local/domain/0/backend/vbd/373/2064/feature-flush-cache.
312705024 sectors of 512 bytes
**************************

[H
[J

GNU GRUB version 0.97 (1740800K lower / 0K upper memory)



[ Minimal BASH-like line editing is supported. For

the first word, TAB lists possible command

completions. Anywhere else TAB lists the possible

completions of a device/filename. ]




grubdom>
[9;10H




Has anyone encountered this or similar issue?

Another issue that I faced is that when the micro bosh instance is
restarted
the agent doesn't startup cleanly complaining about aws registry
which
complains about nats_server and nats_server complains about some
components
missing. What is the standard way to start agent service and the
rest
of the
required components?

Thanks in advance!


--
cheers,
/Martin
--
Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid
enough."


--
cheers,
/Martin
--
Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid
enough."

Search Discussions

Discussion Posts

Previous

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 7 of 7 | next ›
Discussion Overview
groupbosh-users @
postedAug 2, '12 at 1:51p
activeAug 3, '12 at 11:08a
posts7
users3

People

Translate

site design / logo © 2022 Grokbase