service mongodb restart.
> 3) Confirmed mongodb is running(mongodb start/running, process 15257)
> 4) Did a telnet 10.112.107.107 27017 and yes it is working now!
>
>
> Thanks a lot for your efforts!
>
>
> On Tue, Jul 2, 2013 at 3:26 PM, Ashok Kumaran wrote:
>
>>
Hi Chandler,
whats your libvirt_vif_driver set in nova-compute.conf?
On Tue, Jun 18, 2013 at 1:08 PM, Chandler Li wrote:
> Hi, Aaron,
>
> Sorry for my unclear explanation.
>
> I can ping or ssh into the VM with default security group even there are
> no rules setting...
>
> Here is my security
Hi Yuling,
You may need to check the security group rules , ensure that the security
group allows ICMP and ssh(22) in case you are looking for ssh access,
Regards,
Ashok
On Sat, Jun 15, 2013 at 7:10 AM, wrote:
> Hi All,
>
> From openstack documentation, it seems that if we need to crea
Thanks Salv for the crystal clear explanation . Sorry my context was based
on without namespaces scenario . I did not think from namespaces point of
view .
Regards
Ashok
Sent from my iPhone
On 23-May-2013, at 7:52 PM, Salvatore Orlando wrote:
On 23 May 2013 13:15, Ashok Kumaran wrote
Since you have a single node installation , for connecting to the VM's from
the base host you won't need router/l3 stuffs.if its not happening then you
might need to check the secgroup rules.
Coming back to your question. Does the ifconfig shows internal router
interface ip ? have you added the r
Hi Chu,
You might want to check this link.
http://docs.openstack.org/trunk/openstack-network/admin/content/adv_cfg_l3_agent_multi_extnet.html
you can create multiple floating ip pools in association with different ext
nets
-Ashok
On Thu, May 23, 2013 at 10:38 AM, Chu Duc Minh wrote:
> Hi, t
. I can't resolv
> the hosts from my instances.
>
> Thanks
> Paras.
>
>
> On Fri, May 17, 2013 at 3:10 PM, Ashok Kumaran
> wrote:
>
>> It will not populate the external DNS ip in your resolv.conf . Instead
>> the external DNS will be used by the local qua
; I did that but still seeing the same ip on resolv.conf.
>
> Paras.
>
>
> On Fri, May 17, 2013 at 2:17 PM, Ashok Kumaran
> wrote:
>
>> I am assuming that you have a DNS externally and you want the instances
>> to use that DNS. If this is the requirement then
>>
I am assuming that you have a DNS externally and you want the instances to
use that DNS. If this is the requirement then
you will have to add dnsmasq_dns_server= "external DNS IP" in your
/etc/quantum/dhcp_agent.ini.Now your launched instances(VM's) can use
external DNS through quantum dnsmasq.
Pl
guys.
To Kumaran: Do you mean that namespace support should be disabled in DHCP
agent, but why? If I disable namespace in dhcp_agent.ini, is it possible
that something does not work?
On Fri, May 17, 2013 at 6:07 PM, Ashok Kumaran wrote:
> In addition to the below changes set use_namespaces=
In addition to the below changes set use_namespaces=False in dhcp_agent.ini
too.Make sure that your operating system supports network namespaces
Sent from my iPhone
On 17-May-2013, at 3:32 PM, Balamurugan V G wrote:
I am assuming you are using Quantum for networking, in which case make sure
Looks like there could be some configuration issues in libvirtd.conf.
Can you ensure that you have below values set
listen_tls=0
listen_tcp=1
Try restarting libvirt-bin let us know the outcome
-Ashok
Sent from my iPhone
On 11-May-2013, at 1:29 AM, Dhanasekaran Anbalagan
wrote:
Hi Guys,
I tr
Hi Angelo,
This should be possible. Make sure that eth1 is connected to the Vlan trunk
with necessary port configurations.
Create 2 network with segmentation's ID as 108 and 109 respectively. Create
the respective subnets for both network and then proceed with further
configurations as needed. Ar
Ashutosh,
[ Error 111 ] Connection refused as an error.
for the above error you might wanna check your keystone authentication
part. create the service endpoints properly
Ashok
On Wed, May 8, 2013 at 5:52 PM, Ashutosh Narayan wrote:
> Hi Jay,
>
> The log file ( /var/log/quantum/server.log) t
Hi Liu,
Have you done the below step? which actually attaches the router with the
specified network,
quantum router-interface-add $router_id $net1_ID
quantum router-interface-add $router-id $net2_ID
Regards,
Ashok
On Mon, May 6, 2013 at 3:02 PM, Liu Wenmao wrote:
> Hi list:
>
> I set up qua
Hi Jing,
In a single Nic for simulation purpose you can segregate the
data/management network and the external network using Vlan tags.
Lets say your management network lies in vlan 20 and data network in 21 and
the external one in vlan 22 then you can point eth0 to vlan20 and eth0.21
to data and
Can you share the following configuration files
/etc/default/quantum-server, quantum.conf, quantum dhcp conf?
On Thu, May 2, 2013 at 4:15 PM, Arindam Choudhury wrote:
> Hi,
>
> I am very new to openstack. I am trying to install grizzly with quantum
> using gre and tunneling.
>
> # nova-manage
I echo Eric ,minimum we would be needing one IP for router gateway
interface and and one for the allocation, so dont use /32. Just my opinion
Regards,
Ashok
On Thu, May 2, 2013 at 4:35 PM, wrote:
> I believe a minimum of 2 IP addresses is required (1 for the bridge port,
> and 1 to allocate).
18 matches
Mail list logo
