Thanks for the information. I think in this case, it would be good if smart
proxy plugin would communicate with platform then. But for easier start you
might start with the foreman plugin only and move the code from foreman plugin
to smart proxy later if you find the need to proxy the communication. I
suppose the plugin would be only talking to the platform and not specific
devices/things.
--
Marek
On pondělí 3. července 2017 10:11:34 CEST Fairouz el ouazi wrote:
> Hello ,
>
>
> My platform is a software suite for IoT / M2M solution integrators
> offering a set of tools to facilitate the interconnection between *devices*
> (or connected *« things »*) and *business applications*:
>
>-
>
>*Connectivity Interfaces* (public and private) to collect data, send
>command or notification from/to IoT/M2M devices,
>-
>
>*Device Management* (supervision, configuration, resources, firmware,
>etc.),
>-
>
>*Message Routing* between devices and business applications,
>-
>
>*Data Management*: *Data Storage* with *Advanced Search* features.
>
> Every device has a particular parameters with a mix of communication modes
> . The devices use MQTT protocol to communicate with the platform .
>
> I m looking for a device management that can offer me more functionalities
> so the clients can have more visibility for their devices . For example i
> want to modify a parameter on multiple devices at the same time : ex:
> device Group . I want to manage different devices with different constraint
> , I want to supervise my devices and their evolution and it will be just
> great if i could do auto-provisioning (my devices get automatically an
> existent configuration and having inventory .
>
> Le lundi 3 juillet 2017 09:16:05 UTC+2, Marek Hulán a écrit :
> > Hello
> >
> > the smart proxy chef plugin is only a proxy between Foreman - chef-client
> > and
> > Foreman - chef-server. Most of Foreman functionality proxies the
> > communication
> > through smart-proxy, the idea is that Foreman is running on one place e.g.
> > in
> > office while you need to talk to many hosts in datacenters. These hosts
> > might
> > not be accessible from outside network so you put smart-proxy to the
> > datacenter and make this as the only available endpoint.
> >
> > It's totally up to you if you decide to go this path, if this is not your
> > case, you can just add one plugin on foreman side. For iot devices it
> > really
> > depends on what you're trying to achieve. Describing that on few examples
> > would help me understand what you need.
> >
> > On pátek 30. června 2017 14:40:53 CEST Fairouz el ouazi wrote:
> > > Hi , it's me again im really sorry for asking a lot of question but when
> > > take a look to the documetation i didn't get a clear idea about the real
> > > job of smart proxy chef plugin and why on chef we have a client plugin
> >
> > and
> >
> > > on salt we don't have it ?? and if my platform is not agent less would
> >
> > it
> >
> > > be necessary to have 3 plugin one on foreman and other one on smart
> >
> > proxy
> >
> > > foreman and the third on my iot devices ?
> > >
> > > Le mercredi 28 juin 2017 11:50:40 UTC+2, Fairouz el ouazi a écrit :
> > > > Hi everyone ,
> > > >
> > > > I'm a beginner in using foreman ,So before in take the adventure
> >
> > i
> >
> > > > want to know if the fact that it exists a plugin for managing chef is
> > > > there
> > > > any chance to develop a new one that will manage my own platform X
> > > > (PLatform that manage IOT devices ) . So at place of having chef
> >
> > client
> >
> > > > i
> > > > will have foreman dealing with the devices of my X platform . ???
> > > >
> > > > I really need your help or some ideas or if anyone has face the
> >
> > same
> >
> > > > uses cases ?
--
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
