文件列表:

.formatter.exs (91, 2021-04-06)
assets/ (0, 2021-04-06)
assets/.babelrc (55, 2021-04-06)
assets/css/ (0, 2021-04-06)
assets/css/app.scss (629, 2021-04-06)
assets/css/phoenix.css (10310, 2021-04-06)
assets/js/ (0, 2021-04-06)
assets/js/app.js (489, 2021-04-06)
assets/js/socket.js (2224, 2021-04-06)
assets/package.json (765, 2021-04-06)
assets/static/ (0, 2021-04-06)
assets/static/config_gen/ (0, 2021-04-06)
assets/static/config_gen/test.cfg (0, 2021-04-06)
assets/static/favicon.ico (1258, 2021-04-06)
assets/static/images/ (0, 2021-04-06)
assets/static/images/phoenix.png (13900, 2021-04-06)
assets/static/onbox_streamer/ (0, 2021-04-06)
assets/static/onbox_streamer/onbox_streamer.py (1248, 2021-04-06)
assets/static/podvars.yml (304, 2021-04-06)
assets/static/robots.txt (202, 2021-04-06)
assets/static/templates/ (0, 2021-04-06)
assets/static/templates/conf_nxv.eex (2186, 2021-04-06)
assets/webpack.config.js (1524, 2021-04-06)
config/ (0, 2021-04-06)
config/config.exs (999, 2021-04-06)
config/dev.exs (1935, 2021-04-06)
config/prod.exs (2033, 2021-04-06)
config/prod.secret.exs (951, 2021-04-06)
config/test.exs (273, 2021-04-06)
lib/ (0, 2021-04-06)
lib/poap_server.ex (257, 2021-04-06)
lib/poap_server/ (0, 2021-04-06)
lib/poap_server/application.ex (980, 2021-04-06)
lib/poap_server_web.ex (1929, 2021-04-06)
lib/poap_server_web/ (0, 2021-04-06)
lib/poap_server_web/channels/ (0, 2021-04-06)
lib/poap_server_web/channels/user_socket.ex (1100, 2021-04-06)
... ...

# DCAUI_POAP_SERVER Practice POAP/After Power on Auto Provisioning Server for Cisco Automating Data Center Solutions. Inspired by Cisco DCAUTI CDLL Training. The Original code from Cisco CDLL is written in Python. Since Elixir are more efficient at message passing and multithreading, theoretically Elixir should be more suitable for POAP Server. In original Python script, the author use Jinja2 as templet language. In this project, we use Elixir EEx - Embedded Elixir. The purpose of this code base is to test the difference when running the POAP server in Python and Elixir. For example, efficiency, stability and code complexity. The code is based on Elixir Pheonix. ## Current Function Supported * Pull config with http request with EEx dynamic config adjustent. For example, dynamic mgmt0 IP address allocation from yaml file. - API: `/conf. ` * Pull NXOS image with md5 file with http request - API: `/nxos. ` * Pull the element above with Cisco POAP Script for NXOS * After power on auto provisioning from guestshell - API: `/onbox_streamer ` (NEW!!) ## Sample use case * Pull Config On Nexus: ``` [admin@guestshell ~]$ curl 172.26.138.181:4000/conf.9EZ8IGDBM5 ``` * After power on auto provisioning from guestshell On Nexus: ``` N9K1(config-if)# run guestshell [admin@guestshell ~]$ curl 172.26.138.181:4000/onbox_streamer > onbox_streamer.py [admin@guestshell ~]$ python onbox_streamer.py 172.26.138.181 4000 ``` * Retrive NXOS Firmware On Nexus: ``` [admin@guestshell ~]$ curl 172.26.138.181:4000/nxos.7.0.3.I7.9.bin ``` ## Variables and Resources Most of the mandatory Resources is under `assets/static` folder. Please modify it beforehand. * nxos_fw -> NXOS system software. For example: nxos.7.0.3.I7.9.bin. * tempates -> configuration EEx templets. In the old python code, this is written in Jinja2. * podvars.yml -> Configuration parameter that will be used to fill into the EEx templets. `pod` is the Global Network Variable and `switches` is the the Local Switch Variable per Device. * config_gen -> the config that will be generated before stream to the end device. This folder does not auto clean function at moment which means it does not follow the EU GDPR Regulations. * onbox_streamer -> Retreive onbox streamer script from the server. This is used for after power on provisioning from guestshell ## Main Controller `/lib/poap_server_web/controllers/page_controller.ex` ## External Resource Nexus POAP Script From Cisco https://github.com/datacenter/nexus9000/blob/master/nx-os/poap/poap.py. Cisco Nexus 9000 Series NX-OS Fundamentals Configuration Guide, Release 7.x https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/fundamentals/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_Fundamentals_Configuration_Guide_7x/b_Cisco_Nexus_9000_Series_NX-OS_Fundamentals_Configuration_Guide_7x_chapter_0100.html ## Test Bed The POAP Script is run with the following option: ``` options = { "username": "tftp", "password": "x", "hostname": "192.168.46.130:4000", "transfer_protocol": "http", "mode": "serial_number", "target_system_image": "nxos.7.0.3.I7.9.bin", "disable_md5": False, "use_nxos_boot": True, "bypass_bios": True <<< customized parameter } ``` The poap script that used for testing can be found in the "test_poap_script" folder. Suggest to test the library with Cisco Devnet Sandbox: NXOS: https://devnetsandbox.cisco.com/RM/Diagram/Index/0e22761d-f813-415d-a557-24fa0e17ab50?diagramType=Topology OR With Nexus9000v. Sample testbed connectivity ``` Nexus 9000v <-(serial connection: minicom ttyS1, Management: Virtual Network Mgmt, Data: Virtual Network Data) -> Ubuntu ``` ## Main Repositiory https://github.com/GiantPanda0090/DCAUI_ToolSet ## Development/Test Enviorment * Erlang/OTP 23 * Elixir (1.11.2) * Mix 1.11.2 (compiled with Erlang/OTP 23) ## Installation Method Phoenix installation: https://hexdocs.pm/phoenix/installation.html To start your Phoenix server: * Install dependencies with `mix deps.get` * Install Node.js dependencies with `npm install` inside the `assets` directory * Start Phoenix endpoint with `mix phx.server` Now you can visit [`localhost:4000`](http://localhost:4000) from your browser. Ready to run in production? Please [check our deployment guides](https://hexdocs.pm/phoenix/deployment.html). ## Learn more * Official website: https://www.phoenixframework.org/ * Guides: https://hexdocs.pm/phoenix/overview.html * Docs: https://hexdocs.pm/phoenix * Forum: https://elixirforum.com/c/phoenix-forum * Source: https://github.com/phoenixframework/phoenix

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：