[Ipmitool-devel] Ericsson OEM extensions

[Jens Nyberg]

Hi,

My name is Jens Nyberg and I work as part of a team at Ericsson that
currently are working on IPMI support for Ericsson Blade Systems
(EBS). Previous iterations of these systems had been using there own
specialized IPMI protocol which was incompatible with the standard but
for the next generation we are trying to conform more to the standard
protocol.

We have, besides supporting some of the default ipmi commands, also
developed an extension. This extension uses the keyword ericssonoem,
the same way as you have sunoem or delloem today.

I now would like to know what is the recommended way for us to share
our extension upstream? I have forked the git repository on
Sourceforge and I assume all I need to do is to create a merge request
once I have uploaded the changes?

As far as the changes involved they are pretty straightforward so they
shouldn't be invasive at all. They are currently based on the latest
tagged commit but we could easily rebase it to the latest master if
you prefer. I assume ipmitool is one-track?

Thanks

/ Jens

[Hank Bruning]

Send the IPMI extensions to me so JBlade can add them to the Hemi IPMI
library.
http://www.jblade.com/products/hemi/hemiDC/HemiDcOverview.jsf
Also can you add a higher level description on the interactions so that we
can add it to the Hemi Programmers API which is on the left side bottom of
the page?
Regards,
hank bruning

Post by Jens Nyberg
Hi,
My name is Jens Nyberg and I work as part of a team at Ericsson that
currently are working on IPMI support for Ericsson Blade Systems
(EBS). Previous iterations of these systems had been using there own
specialized IPMI protocol which was incompatible with the standard but
for the next generation we are trying to conform more to the standard
protocol.
We have, besides supporting some of the default ipmi commands, also
developed an extension. This extension uses the keyword ericssonoem,
the same way as you have sunoem or delloem today.
I now would like to know what is the recommended way for us to share
our extension upstream? I have forked the git repository on
Sourceforge and I assume all I need to do is to create a merge request
once I have uploaded the changes?
As far as the changes involved they are pretty straightforward so they
shouldn't be invasive at all. They are currently based on the latest
tagged commit but we could easily rebase it to the latest master if
you prefer. I assume ipmitool is one-track?
Thanks
/ Jens
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel

[Jim Mankovich]

Jens,
Create a patch based on the current TOB git repository and submit a
patch ticket to ipmitool with documentation pertaining to the change
along with the patch.

Please take time to updated the man page if you have not already done so.

Jim

Post by Jens Nyberg
Hi,
My name is Jens Nyberg and I work as part of a team at Ericsson that
currently are working on IPMI support for Ericsson Blade Systems
(EBS). Previous iterations of these systems had been using there own
specialized IPMI protocol which was incompatible with the standard but
for the next generation we are trying to conform more to the standard
protocol.
We have, besides supporting some of the default ipmi commands, also
developed an extension. This extension uses the keyword ericssonoem,
the same way as you have sunoem or delloem today.
I now would like to know what is the recommended way for us to share
our extension upstream? I have forked the git repository on
Sourceforge and I assume all I need to do is to create a merge request
once I have uploaded the changes?
As far as the changes involved they are pretty straightforward so they
shouldn't be invasive at all. They are currently based on the latest
tagged commit but we could easily rebase it to the latest master if
you prefer. I assume ipmitool is one-track?
Thanks
/ Jens
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
--

[Zdenek Styblik]

Post by Jim Mankovich
Jens,
Create a patch based on the current TOB git repository and submit a
patch ticket to ipmitool with documentation pertaining to the change
along with the patch.
Please take time to updated the man page if you have not already done so.
Jim

Thought should be given whether or not to split man page into smaller
ones. It's 3.5k lines already and I'm not sure this is user friendly.

Z.

Post by Jim Mankovich

Post by Jens Nyberg
Hi,
My name is Jens Nyberg and I work as part of a team at Ericsson that
currently are working on IPMI support for Ericsson Blade Systems
(EBS). Previous iterations of these systems had been using there own
specialized IPMI protocol which was incompatible with the standard but
for the next generation we are trying to conform more to the standard
protocol.
We have, besides supporting some of the default ipmi commands, also
developed an extension. This extension uses the keyword ericssonoem,
the same way as you have sunoem or delloem today.
I now would like to know what is the recommended way for us to share
our extension upstream? I have forked the git repository on
Sourceforge and I assume all I need to do is to create a merge request
once I have uploaded the changes?
As far as the changes involved they are pretty straightforward so they
shouldn't be invasive at all. They are currently based on the latest
tagged commit but we could easily rebase it to the latest master if
you prefer. I assume ipmitool is one-track?
Thanks
/ Jens
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
--

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel

[Zdenek Styblik]

Post by Jens Nyberg
Hi,
My name is Jens Nyberg and I work as part of a team at Ericsson that
currently are working on IPMI support for Ericsson Blade Systems
(EBS). Previous iterations of these systems had been using there own
specialized IPMI protocol which was incompatible with the standard but
for the next generation we are trying to conform more to the standard
protocol.
We have, besides supporting some of the default ipmi commands, also
developed an extension. This extension uses the keyword ericssonoem,
the same way as you have sunoem or delloem today.
I now would like to know what is the recommended way for us to share
our extension upstream? I have forked the git repository on
Sourceforge and I assume all I need to do is to create a merge request
once I have uploaded the changes?

Please, see http://sourceforge.net/p/ipmitool/wiki/coding_standards/
before you post anything.

Thanks,
Z.

Post by Jens Nyberg
As far as the changes involved they are pretty straightforward so they
shouldn't be invasive at all. They are currently based on the latest
tagged commit but we could easily rebase it to the latest master if
you prefer. I assume ipmitool is one-track?
Thanks
/ Jens
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel