-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
juniper_junos_jsnapy issue with Vagrant vQFX #430
Comments
@gmoisio The support to specify custom file names is already present in JSNAPy, but is not currently supported via Ansible module: juniper_junos_jsnappy. Marking as an enhancement. Thanks for reporting the feature, will work on it and raise a PR. Are there any specifics or ideas you think should be included in the feature ?? |
Hi, thank you for your answer. Using the snap_file_name parameter as in JSNAPy would be great. Thanks |
Hi, one more question please.
--Python code--
Thanks |
There is no such feature in Jsnapy, but this would be a nice feature to have. Will work on it and keep you posted. |
@rahkumar651991 Can you please take a look at this ?? |
Hi ,
Thanks |
Issue Type: Feature Idea
Module Name: juniper_junos_jsnapy
Last Master Juniper.Junos role and last Python libraries version
Using Vagrant vQFX and Ansible provisioning to simulate a network, there is an issue with juniper_junos_jsnapy module.
The inventory file generated by Vagrant use a specific generated inventory_hostname for each device, but the ansible_host is the same (127.0.0.1). Difference is made with ansible_port for each device.
JSNAPy use the IP address for the snap files. It's the same for each device, so we do not get the expected behavior in a simulation environment.
Is there a trick to change the way JSNAPy records the snap files names?
Thanks
Regards
The text was updated successfully, but these errors were encountered: