attachments, which I missed in earlier email, here.
On Sat, Feb 25, 2017 at 5:57 AM, Rupinder Singh <[email protected]> wrote:
> Hi Svet,
> Thanks for your continued support.
> I tried to change Vagrantfile as attached here in raw. The output remains
> as before as attached here.
>
> Rupinder
>
> On Fri, Feb 24, 2017 at 9:42 PM, Svetoslav Neykov <svetoslav.neykov@
> cloudsoftcorp.com> wrote:
>
>> Hi rupinder,
>>
>> In the Vagrantfile try to disable virtualization. Insert the following
>> before the end of the configure section [1]:
>>
>> config.vm.provider :virtualbox do |vb|
>> vb.customize ["modifyvm", :id, "--hwvirtex", "off"]
>> end
>>
>> Svet.
>>
>> [1] https://github.com/apache/brooklyn-dist/blob/c9c688ccdea1508
>> 17800b05d0a39aa0e812e27f4/vagrant/src/main/vagrant/Vagrantfile#L84
>>
>> > On 24.02.2017 г., at 18:06, Rupinder Singh <[email protected]> wrote:
>> >
>> > 1. my pc doesn't have VT-X for sure.
>> >
>> > 2. But I run ubuntu out of Oracle VirtualBox and installation works.
>> >
>> > rupinder
>> >
>> >
>> >
>> > On Mon, Feb 20, 2017 at 9:02 PM, Rupinder Singh <[email protected]>
>> wrote:
>> >>
>> >>
>> >> Hi Svet
>> >> 1. No. I am not running vagrant inside another VM.
>> >>
>> >> 2. Windows 7. So it doesn't have hyper-V installed.
>> >>
>> >> rupinder
>> >>
>> >> On Mon, Feb 20, 2017 at 8:43 PM, Svetoslav Neykov <
>> > [email protected]> wrote:
>> >>>
>> >>> Hi Rupinder,
>> >>>
>> >>> If your machine doesn't support virtualisation you can still give
>> > Brooklyn a try by executing it directly in Windows.
>> >>> Download the zip[1] archive, extract it and run "bin/brooklyn launch"
>> > from the extracted folder. You can configure a cloud location
>> >>> and deploy an example blueprint to it. Drop by in our IRC channel
>> > #brooklyncentral (on FreeNode) if you need guidance on how to do that.
>> >>>
>> >>> Having said that, all recent processors should support virtualisation.
>> > If you don't have the option it could mean that it's already enabled.
>> >>> The error you get could (alternatively) be caused by one of the
>> > following:
>> >>> * You are trying to run vagrant inside another VM. Is your Windows
>> > running locally in a VM? Are you working through an RDP session?
>> >>> * You have Hyper-V (which is Microsoft's alternative to Virtualbox)
>> > enabled. Need to disable it - see the stackoverflow link sent by Mike
>> below.
>> >>>
>> >>>
>> >>> Svet.
>> >>>
>> >>>
>> >>> [1]
>> > https://www.apache.org/dyn/closer.lua?action=download&filena
>> me=brooklyn/apache-brooklyn-0.10.0/apache-brooklyn-0.10.0-bin.zip
>> >>>
>> >>>
>> >>>> On 20.02.2017 г., at 16:13, Rupinder Singh <[email protected]>
>> wrote:
>> >>>>
>> >>>> I have Compaq R191B. Virtualization option is not there in BIOS.
>> > Doesn't
>> >>>> support VT-X.
>> >>>>
>> >>>> On Mon, Feb 20, 2017 at 1:06 AM, Valentin Aitken <
>> >>>> [email protected]> wrote:
>> >>>>
>> >>>>> Hi Rupinder,
>> >>>>>
>> >>>>> The last log says vagrant cannot find rsync.
>> >>>>> Could you try installing and adding to PATH some Windows port of
>> > rsync?
>> >>>>> I suggest to try Cygwin [1].
>> >>>>>
>> >>>>> Valentin.
>> >>>>>
>> >>>>> [1] https://en.wikipedia.org/wiki/Cygwin
>> >>>>>
>> >>>>> На 19/02/17 в 18:25, Rupinder Singh написа:
>> >>>>>
>> >>>>>> Hi Mark, Duncan,
>> >>>>>>
>> >>>>>> Fresh output is as attached. Would this work?
>> >>>>>>
>> >>>>>> Rupinder
>> >>>>>>
>> >>>>>> On Sun, Feb 19, 2017 at 8:45 PM, Rupinder Singh <
>> [email protected]
>> >>>>>> <mailto:[email protected]>> wrote:
>> >>>>>>
>> >>>>>> Thanks Mark, Duncan!
>> >>>>>>
>> >>>>>> I'll try out and revert.
>> >>>>>>
>> >>>>>> Rupinder
>> >>>>>>
>> >>>>>> On Sun, Feb 19, 2017 at 8:28 PM, Mark Mc Kenna
>> >>>>>> <[email protected] <mailto:[email protected]>> wrote:
>> >>>>>>
>> >>>>>> Hi Rupinder,
>> >>>>>>
>> >>>>>> As Duncan said the ubuntu image is no longer supported by
>> > vagrant.
>> >>>>>>
>> >>>>>> The updated centos7 version can be downloaded from the apache
>> >>>>>> maven repo
>> >>>>>> [1]
>> >>>>>> It is worth noting that this is configured for the
>> >>>>>> 0.11.0-SNAPSHOT version
>> >>>>>> of brooklyn. To change this please amend BROOKLYN_VERSION in
>> >>>>>> servers.yaml
>> >>>>>> [2].
>> >>>>>>
>> >>>>>> I have confirmed the above is working for
>> >>>>>> vagrant: 1.9.1
>> >>>>>> virtualbox: 5.0.30 r112061
>> >>>>>>
>> >>>>>> [1]
>> >>>>>> https://repository.apache.org/content/groups/snapshots/org/a
>> >>>>>> pache/brooklyn/brooklyn-vagrant/0.11.0-SNAPSHOT/
>> >>>>>> <https://repository.apache.org/content/groups/snapshots/org/
>> >>>>>> apache/brooklyn/brooklyn-vagrant/0.11.0-SNAPSHOT/>
>> >>>>>> [2]
>> >>>>>> https://github.com/apache/brooklyn-dist/blob/master/vagrant/
>> >>>>>> src/main/vagrant/servers.yaml#L50
>> >>>>>> <https://github.com/apache/brooklyn-dist/blob/master/vagrant
>> >>>>>> /src/main/vagrant/servers.yaml#L50>
>> >>>>>>
>> >>>>>> Cheers
>> >>>>>>
>> >>>>>> *Mark McKenna*
>> >>>>>>
>> >>>>>> *Web :: markmckenna.ie <http://markmckenna.ie>
>> >>>>>> <http://markmckenna.ie/>*
>> >>>>>>
>> >>>>>> *Work :: [email protected]
>> >>>>>> <mailto:[email protected]> <
>> [email protected]
>> >>>>>> <mailto:[email protected]>>*
>> >>>>>>
>> >>>>>> *PGP :: A7A9 24DE 638C 681A 8DEA FAD4 2B5D C759 B1EB 76A7
>> >>>>>> <
>> > https://pgp.mit.edu/pks/lookup?op=get&search=0x2B5DC759B1EB76A7
>> >>>>>> <
>> > https://pgp.mit.edu/pks/lookup?op=get&search=0x2B5DC759B1EB76A7
>> >>>>>>>> *
>> >>>>>>
>> >>>>>> On 19 February 2017 at 13:15, Duncan Godwin
>> >>>>>> <[email protected]
>> >>>>>> <mailto:[email protected]>
>> >>>>>>> wrote:
>> >>>>>>
>> >>>>>>> Hi Rupinder
>> >>>>>>>
>> >>>>>>> So I imagine the version of Ubuntu used in the vagrant
>> >>>>>> example is no
>> >>>>>>> longer supported. Fortunately this was upgraded a few weeks
>> >>>>>> ago to centos
>> >>>>>>> 7. This is expected in version 0.11 but is currently
>> >>>>>> available in the
>> >>>>>>> snapshot version here:
>> >>>>>>>
>> >>>>>>> https://brooklyn.apache.org/meta/versions.html
>> >>>>>> <https://brooklyn.apache.org/meta/versions.html>
>> >>>>>>>
>> >>>>>>> Thanks
>> >>>>>>>
>> >>>>>>> Duncan
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> On 19 Feb 2017 13:08, "Richard Downer" <[email protected]
>> >>>>>> <mailto:[email protected]>> wrote:
>> >>>>>>>
>> >>>>>>> Hi Rupinder,
>> >>>>>>>
>> >>>>>>> A few months back on an unrelated project I had a similar
>> >>>>>> problem and it
>> >>>>>>> was caused by a bug in Vagrant on Windows. I can't remember
>> >>>>>> the details and
>> >>>>>>> I'm on the road at the moment so I can't look it up, but it
>> >>>>>> may be worth
>> >>>>>>> searching Google for the error message. When I'm back in the
>> >>>>>> office I'll
>> >>>>>>> see if I can find more details for you.
>> >>>>>>>
>> >>>>>>> Sent from my Android phone
>> >>>>>>>
>> >>>>>>> On 19 Feb 2017 1:35 a.m., "Rupinder Singh"
>> >>>>>> <[email protected] <mailto:[email protected]>> wrote:
>> >>>>>>>
>> >>>>>>> Hi Mark,
>> >>>>>>>
>> >>>>>>> The output from those two commands is as attached.
>> >>>>>>>
>> >>>>>>> vagrant version is 1.9.1
>> >>>>>>>
>> >>>>>>> thanks
>> >>>>>>>
>> >>>>>>> On Sat, Feb 18, 2017 at 10:54 PM, Mark Mc Kenna
>> >>>>>> <[email protected] <mailto:[email protected]>>
>> >>>>>>> wrote:
>> >>>>>>>
>> >>>>>>>> Hi Rupinder,
>> >>>>>>>> Can you try running the below commands and provide the
>> >>>>>> output ... Also
>> >>>>>>> can
>> >>>>>>>> you provide the vagrant version
>> >>>>>>>>
>> >>>>>>>> vagrant box add ubuntu/wily64
>> >>>>>>>> vagrant up
>> >>>>>>>>
>> >>>>>>>> Cheers
>> >>>>>>>> Mark
>> >>>>>>>>
>> >>>>>>>> On 18 Feb 2017 16:44, "Rupinder Singh" <[email protected]
>> >>>>>> <mailto:[email protected]>> wrote:
>> >>>>>>>>
>> >>>>>>>> I am beginner in brooklyn. I am trying to bring up
>> >>>>>> brooklyn from vagrant
>> >>>>>>> on
>> >>>>>>>> my windows 7 machine. I am getting 404 error
>> >>>>>>>>
>> >>>>>>>> downloading
>> >>>>>>>> https://atlas.hashicorp.com/ubuntu/boxes/wily64/versions/
>> >>>>>> <https://atlas.hashicorp.com/ubuntu/boxes/wily64/versions/>
>> >>>>>>>> 20160715.0.0/providers/virtualbox
>> >>>>>>>>
>> >>>>>>>> thats from where it says. file not found 404
>> >>>>>>>>
>> >>>>>>>> can anybody help?
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>> --
>> >>>>> Valentin Aitken
>> >>>>> Software Engineer
>> >>>>> Cloudsoft Corporation Ltd.
>> >>>>> www.cloudsoft.io
>> >>>>>
>> >>>>>
>> >>>
>> >>
>>
>>
>
C:\brooklyn>vagrant up brooklyn
Bringing machine 'brooklyn' up with 'virtualbox' provider...
==> brooklyn: Checking if box 'centos/7' is up to date...
==> brooklyn: Clearing any previously set forwarded ports...
==> brooklyn: Clearing any previously set network interfaces...
==> brooklyn: Preparing network interfaces based on configuration...
brooklyn: Adapter 1: nat
==> brooklyn: Forwarding ports...
brooklyn: 8081 (guest) => 8081 (host) (adapter 1)
brooklyn: 22 (guest) => 2222 (host) (adapter 1)
==> brooklyn: Running 'pre-boot' VM customizations...
==> brooklyn: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "cc61e034-77c0-4be4-9e16-931cc999c439", "--type", "headless
"]
Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap,
interface IConsole
C:\brooklyn>
# -*- mode: ruby -*-
# vi: set ft=ruby :
#
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements. See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership. The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License. You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
#
# Specify minimum Vagrant version and Vagrant API version
Vagrant.require_version ">= 1.8.1"
VAGRANTFILE_API_VERSION = "2"
# Update OS (Debian/RedHat based only)
UPDATE_OS_CMD = "(sudo apt-get update && sudo apt-get -y upgrade) || (sudo yum
-y update)"
# Autocorrect Port Clashes
DEFAULT_AUTOCORRECT = false
# Require YAML module
require 'yaml'
# Read YAML file with box details
yaml_cfg = YAML.load_file(__dir__ + '/servers.yaml')
# Create boxes
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
# Iterate through server entries in YAML file
yaml_cfg["servers"].each do |server|
config.vm.define server["name"] do |server_config|
server_config.vm.box = server["box"]
server_config.vm.box_check_update =
yaml_cfg["default_config"]["check_newer_vagrant_box"]
if server.has_key?("ip")
server_config.vm.network "private_network", ip: server["ip"]
end
if server.has_key?("forwarded_ports")
server["forwarded_ports"].each do |port|
if port.has_key?("autocorrect")
autocorrect = true
else
autocorrect = DEFAULT_AUTOCORRECT
end
server_config.vm.network "forwarded_port", guest: port["guest"],
host: port["host"], guest_ip: port["guest_ip"], autocorrect: autocorrect
end
end
server_config.vm.hostname = server["name"]
server_config.vm.provider :virtualbox do |vb|
vb.name = server["name"]
vb.memory = server["ram"]
vb.cpus = server["cpus"]
end
if yaml_cfg["default_config"]["run_os_update"]
server_config.vm.provision "shell", privileged: false, inline:
UPDATE_OS_CMD
end
if server["shell"] && server["shell"]["cmd"]
server["shell"]["cmd"].each do |cmd|
server_config.vm.provision "shell", privileged: false, inline: cmd,
env: server["shell"]["env"]
end
end
server_config.vm.post_up_message = server["post_up_message"]
end
end
config.vm.provider :virtualbox do |vb|
vb.customize ["modifyvm", :id, "--hwvirtex", "off"]
end
end
# ALTERING PORT FORWARDING
# If you are reading this you have likely been instructed by Vagrant to alter
the example
# line below due to the forwarded port colliding with one alread in use on your
system.
#
# config.vm.network :forwarded_port, guest: 80, host: 1234
#
# This Vagrantfile does not define the port mapping here, instead you should
alter
# the following line in the `servers.yaml` file in this directory.
#
# host: 8081
#
# Change 8081 to a port that is not in use on your local machine before
attempting
# to run vagrant up again.
