airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pankaj Saha <psa...@binghamton.edu>
Subject Re: Testing request for Ansible playbooks!
Date Mon, 10 Apr 2017 21:24:33 GMT
Yes .
We can see the PGA installed and running on port 80 of the VM.

Thanks
Pankaj

On Mon, Apr 10, 2017 at 5:17 PM, Pankaj Saha <psaha4@binghamton.edu> wrote:

> Hi Eric,
> Yes,
> That was the issue with NAT while creating VMs. Looks like it's resolved
> and running now.
>
> Thanks
> Pankaj
>
> On Mon, Apr 10, 2017 at 5:03 PM, Eric Coulter <jecoulte@iu.edu> wrote:
>
>> Hi Pankaj,
>>
>> Can you double-check that networking is working properly on the VM? How
>> many interfaces did you create?
>>
>> I typically have a NAT interface enabled, and a host-only interface
>> (which would be the 192.168.56.102 address) - the NAT should allow easy
>> access to the outside world (yum repositories, mostly) without too much
>> trouble, but often isn't automatically configured to start on boot.
>>
>> To check whether this is enabled, use
>> `nmcli connection show $nat_device_name | grep auto`, and if you see 'no'
>> or 'false', use
>>
>> `nmcli connection modify $nat_device connection.autoconnect yes`
>>
>> You can also check whether it's up by running `nmcli con show`, and the
>> 'up' interfaces should show up in green.
>>
>> Cheers,
>> Eric C.
>> On 04/10/2017 04:48 PM, Pankaj Saha wrote:
>>
>> Hi
>> I am getting this error for one of my MV machines.
>>
>> < TASK [env_setup : Install Firewalld (RedHat)] >
>>  -----------------------------------------------
>>         \   ^__^
>>          \  (oo)\_______
>>             (__)\       )\/\
>>                 ||----w |
>>                 ||     ||
>>
>>
>> fatal: [192.168.56.102]: FAILED! => {"changed": false, "failed": true,
>> "msg": "\n\n One of the configured repositories failed (Unknown),\n and yum
>> doesn't have enough cached data to continue. At this point the only\n safe
>> thing yum can do is fail. There are a few ways to work \"fix\" this:\n\n
>>   1. Contact the upstream for the repository and get them to fix the
>> problem.\n\n     2. Reconfigure the baseurl/etc. for the repository, to
>> point to a working\n        upstream. This is most often useful if you are
>> using a newer\n        distribution release than is supported by the
>> repository (and the\n        packages for the previous distribution release
>> still work).\n\n     3. Run the command with the repository temporarily
>> disabled\n            yum --disablerepo=<repoid> ...\n\n     4. Disable the
>> repository permanently, so yum won't use it by default. Yum\n        will
>> then just ignore the repository until you permanently enable it\n
>>  again or use --enablerepo for temporary usage:\n\n
>>  yum-config-manager --disable <repoid>\n        or\n
>>  subscription-manager repos --disable=<repoid>\n\n     5. Configure the
>> failing repository to be skipped, if it is unavailable.\n        Note that
>> yum will try to contact the repo. when it runs most commands,\n        so
>> will have to try and fail each time (and thus. yum will be be much\n
>>  slower). If it is a very temporary problem though, this is often a nice\n
>>        compromise:\n\n            yum-config-manager --save
>> --setopt=<repoid>.skip_if_unavailable=true\n\nCannot find a valid
>> baseurl for repo: base/7/x86_64\n", "rc": 1, "results": []}
>>
>>
>> Thanks
>> Pankaj
>>
>> On Mon, Apr 10, 2017 at 3:39 PM, Gourav Rattihalli <
>> grattih1@binghamton.edu> wrote:
>>
>>> Hi Marcus, Eric,
>>>
>>> Thanks, it's working now, need to setup the ssh keys to complete the
>>> setup. Will let you know if I run into any issues.
>>>
>>> On Mon, Apr 10, 2017 at 3:33 PM, Eric Coulter < <jecoulte@iu.edu>
>>> jecoulte@iu.edu> wrote:
>>>
>>>> Thanks, Marcus!
>>>>
>>>> Sorry for the confusion, Gourav - thanks for checking this out!
>>>>
>>>> Let me know if you run into any other issues!
>>>>
>>>> Eric C.
>>>>
>>>> On 04/10/2017 03:16 PM, Christie, Marcus Aaron wrote:
>>>>
>>>> Gourav,
>>>>
>>>> Looks like Eric copied this from the prod seagrid deployment, which
>>>> uses ansible-vault encryption for storing passwords.
>>>>
>>>> I would recommend you remove everything in
>>>> inventories/local-vbox/group_vars/ and replace it with this file:
>>>> <https://github.com/ECoulter/airavata/blob/develop/dev-tools/ansible/inventories/develop/group_vars/all.yml>
>>>> https://github.com/ECoulter/airavata/blob/develop/dev-
>>>> tools/ansible/inventories/develop/group_vars/all.yml
>>>>
>>>> Thanks,
>>>>
>>>> Marcus
>>>>
>>>>
>>>> On Apr 10, 2017, at 2:30 PM, Gourav Rattihalli <
>>>> <grattih1@binghamton.edu>grattih1@binghamton.edu> wrote:
>>>>
>>>> Hi Eric,
>>>>
>>>> I'm testing the playbooks for local virtual box setup and have
>>>> encountered with the following error:
>>>>
>>>> ERROR! Decryption failed on /Users/GR8/airavata/dev-tools/
>>>> ansible/inventories/local-vbox/group_vars/all/vault.yml
>>>>
>>>> The script is unable to decrypt the following:
>>>>
>>>>
>>>>
>>>> $ANSIBLE_VAULT;1.1;AES256
>>>>
>>>> 653166656537613531343930356332636630626265653233373764343362
>>>> 62613962336165343434
>>>> 3232643663396464353466376433633439376566336463300a6266653163
>>>> 39646633633435396136
>>>> 643331343638303363363635343733333537323765353431666337373833
>>>> 63646530376633363133
>>>> 3836303335373630340a3761646538346631346532366134303737383738
>>>> 39646531343830626662
>>>> 613162616430656338666161333863323538636435623330386138396364
>>>> 33383866333834356433
>>>> 6132353361376633313032643464346464623161653663373862
>>>>
>>>> Any idea on how to fix this?
>>>> On Fri, Mar 31, 2017 at 12:53 PM, Eric Coulter <jecoulte@iu.edu>
>>>> wrote:
>>>>>
>>>>> Greetings, All! I've got two new sets of playbooks up at
>>>>> https://github.com/ECoulter/airavata/tree/develop/dev-tools/ansible
>>>>> for deployment of the Airavata stack on either Jetstream of locally using
>>>>> VMs in VirtualBox. (See README sections - each location has a different
>>>>> main playbook and inventory directory.) Hopefully, these will start to
ease
>>>>> the workflow of editing code -> deploying changes version -> testing.
>>>>> Before this gets pulled into the main develop branch, can folks try this
>>>>> out and report back with problems/comments? Thanks! --
>>>>> ------------------------------------ Eric Coulter
>>>>> jecoulte@iu.edu XSEDE Capabilities and Resource Integration Engineer
>>>>> IU Campus Bridging & Research Infrastructure RT/PTI/UITS 812-856-3250
>>>>
>>>> --
>>>> Regards,
>>>> Gourav Rattihalli
>>>>
>>>> --
>>>> ------------------------------------
>>>> Eric Coulter         jecoulte@iu.edu
>>>> XSEDE Capabilities and Resource Integration Engineer
>>>> IU Campus Bridging & Research Infrastructure
>>>> RT/PTI/UITS812-856-3250 <%28812%29%20856-3250>
>>>>
>>>> --
>>> Regards,
>>> Gourav Rattihalli
>>>
>> --
>> ------------------------------------
>> Eric Coulter         jecoulte@iu.edu
>> XSEDE Capabilities and Resource Integration Engineer
>> IU Campus Bridging & Research Infrastructure
>> RT/PTI/UITS812-856-3250 <(812)%20856-3250>
>>
>>
>

Mime
View raw message