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
Blog post featuring XLAB on provider operations with Ansible #699
Conversation
|
||
The last post in the series shows how easy it is to run Ansible playbooks triggered by events that are routed through the ManageIQ Automate engine. This post focuses on acquiring the data required by the playbook to actually invoke the operation against the correct inventory item. These data include the event payload and provider's credentials. To show you the complete process, it includes a video with a step-by-step tutorial. | ||
|
||
Enjoy the read! You may contact XLAB at sddc@xlab.si if you have any questions. Or as they like to say... **Get IT done.** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 LGTM
Hmm,,..I thought the expression was "Get ur done". 😄
Please don't merge yet, waiting for feedback from XLAB |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me, only a minor comment.
|
||
## [Dynamic UI for ManageIQ Provider Operations](https://tech.xlab.si/posts/nuage-react-component/) | ||
|
||
This second post describes how mind-blowingly powerful it is to implement frontend for provider operations using React Components. These live in a provider codebase and are totally independent of the ManageIQ UI. You'll learn about this new era of ManageIQ frontend where you can define your own UIs without affecting the core. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...and are totally independent of the ManageIQ UI.
and are totally independent of the other ManageIQ providers' UI.
(Thing is we still depend on ManageIQ UI - we reuse as much components as possible, plus all the styling/coloring/branding, the main difference is we don't collide with other providers' forms)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cybette We've got few minor comments regarding the team name.
|
||
[Happy 2019](https://www.xlab.si/happy2019/)! We kick off this year with a great feature on collaboration. | ||
|
||
In ManageIQ we introduced a model for adding provider features using [Ansible](https://www.ansible.com). Our friends at [XLAB](https://xlab.si) were the first to work with this new technology enablement integrating some cool operations for the [Nuage](http://www.nuagenetworks.net) SDN provider. In this endeavour they used Ansible to implement the provider's CRUD operations through a set of Ansible roles that are available on [Galaxy](https://galaxy.ansible.com/xlab_si). To support these new operations they also created new UI forms using [React.js](https://reactjs.org). These forms are completely tailored to the specific needs of this provider. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In ManageIQ we introduced a model for adding provider features using [Ansible](https://www.ansible.com). Our friends at [XLAB](https://xlab.si) were the first to work with this new technology enablement integrating some cool operations for the [Nuage](http://www.nuagenetworks.net) SDN provider. In this endeavour they used Ansible to implement the provider's CRUD operations through a set of Ansible roles that are available on [Galaxy](https://galaxy.ansible.com/xlab_si). To support these new operations they also created new UI forms using [React.js](https://reactjs.org). These forms are completely tailored to the specific needs of this provider. | |
In ManageIQ we introduced a model for adding provider features using [Ansible](https://www.ansible.com). Steampunk team at [XLAB](https://steampunk.si) was the first to work with this new technology enablement integrating some cool operations for the [Nuage](http://www.nuagenetworks.net) SDN provider. In this endeavour they used Ansible to implement the provider's CRUD operations through a set of Ansible roles that are available on [Galaxy](https://galaxy.ansible.com/xlab_si). To support these new operations they also created new UI forms using [React.js](https://reactjs.org). These forms are completely tailored to the specific needs of this provider. |
|
||
The last post in the series shows how easy it is to run Ansible playbooks triggered by events that are routed through the ManageIQ Automate engine. This post focuses on acquiring the data required by the playbook to actually invoke the operation against the correct inventory item. These data include the event payload and provider's credentials. To show you the complete process, it includes a video with a step-by-step tutorial. | ||
|
||
Enjoy the read! You may contact XLAB at sddc@xlab.si if you have any questions. Or as they like to say... **Get IT done.** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Enjoy the read! You may contact XLAB at sddc@xlab.si if you have any questions. Or as they like to say... **Get IT done.** | |
Enjoy the read! You may contact XLAB Steampunkers at steampunk@xlab.si if you have any questions. Or as they like to say... **Get IT done.** |
Looks great! I've been reading the XLAB blog posts as they've been coming out, and they are really awesome, so I'm glad to see us featuring them on the ManageIQ blog. 👍 |
@Fryguy all credits go to XLAB, even the idea of the post 😄 @gberginc @miha-plesko please confirm the changes are ok. Thanks for your feedback! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks @cybette 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@cybette Thanks!!!
@JPrause @Fryguy please take a look