All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Kiszka" <jan.kiszka@siemens.com>
To: daniel.sangorrin@toshiba.co.jp, cip-dev@lists.cip-project.org
Cc: Venkata.Pyla@toshiba-tsip.com
Subject: Re: [cip-dev] [PATCH 3/3] README: Add steps to build cip-security image
Date: Thu, 30 Jul 2020 07:59:02 +0200	[thread overview]
Message-ID: <de6bb645-59dc-3ecb-82a6-078684e0a2a1@siemens.com> (raw)
In-Reply-To: <OSBPR01MB20533E649110E28C3CB9B5E5D0710@OSBPR01MB2053.jpnprd01.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2809 bytes --]

On 30.07.20 02:07, daniel.sangorrin@toshiba.co.jp wrote:
> Hi Venkata-san
> 
> Maybe Jan didn't see your e-mail because he wasn't in the CC.
> 
>> -----Original Message-----
>> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Venkata Pyla
>> Sent: Friday, July 24, 2020 3:58 PM
>> To: cip-dev@lists.cip-project.org
>> Subject: Re: [cip-dev] [PATCH 3/3] README: Add steps to build cip-security image
>>
>> Hi Jan,
>>
>> On Thu, Jul 23, 2020 at 04:10 PM, Jan Kiszka wrote:
>>
>>>
>>> On 21.07.20 10:16, Venkata Pyla wrote:
>>>> From: venkata <venkata.pyla@toshiba-tsip.com>
>>>>
>>>> Signed-off-by: venkata <venkata.pyla@toshiba-tsip.com>
>>>> ---
>>>>    README.md | 10 ++++++++++
>>>>    1 file changed, 10 insertions(+)
>>>>
>>>> diff --git a/README.md b/README.md
>>>> index bbad1a0..b2c4166 100644
>>>> --- a/README.md
>>>> +++ b/README.md
>>>> @@ -36,6 +36,16 @@ card, run
>>>>        dd
>>> if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-buster-bbb.wic.
>>> img \
>>>>           of=/dev/<medium-device> bs=1M status=progress
>>>>
>>>> +## Building Security target images
>>>> +Building images for QEMU x86-64bit machine
>>>> +
>>>> +    ./kas-docker --isar build --target cip-core-image-security
>>> kas.yml:board-qemu-amd64.yml
>>>> +
>>>> +Run the generated securiy images on QEMU (x86-64bit)
>>>> +
>>>> +    TARGET_IMAGE=cip-core-image-security ./start-qemu.sh amd64
>>>> +
>>>> +
>>>>    ## Community Resources
>>>>
>>>>    TBD
>>>>
>>>
>>> This patch is fine, but I'm missing 4/4: Add this image to CI (same
>>> comment as I had on the MR on gitlab).
>>>
>>
>> Adding cip security image to CI,
>> i need some suggestions to use the current format present in .gitlab-ci.yml
>>
>> Currently i have the below problem for using script deploy-cip-core.sh:
>> 1. image name formation in the script should have another variable
>>           .../$IMG_PREFIX-cip-core-$RELEASE-$TARGET
>>           where $IMG_PREFIX is default to "cip-core-image"  if not specified
>>            for security image it will be passed as 4th argument "cip-core-image-security"
>> 2. currently scrit is expecting the image format in *.wic.img so,
>>         for qemu i think we should have wks file to generate image with format .wic.img
>>
>> or for this security image do we need to deploy it seperatley?
>> please guide me
> 
> Sometimes it is better to send a patch instead of trying to explain it with words.
> 

I've replied on the deployment question already.

If there is a need for the security artifacts already, we need to 
enhance the deployment for that particular use case - but I doubt there 
is at this point, otherwise the series had carried CI in the first place.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#5059): https://lists.cip-project.org/g/cip-dev/message/5059
Mute This Topic: https://lists.cip-project.org/mt/75699595/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2020-07-30  5:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21  8:16 [cip-dev] [PATCH 1/3] cip-security: Add packages for IEC-62443-4-2 Evaluation Venkata Pyla
2020-07-21  8:16 ` [cip-dev] [PATCH 2/3] start-qemu.sh: use TARGET_IMAGE to pick respective image file Venkata Pyla
2020-07-21  8:16 ` [cip-dev] [PATCH 3/3] README: Add steps to build cip-security image Venkata Pyla
2020-07-23 10:40   ` Jan Kiszka
2020-07-24  6:58     ` Venkata Pyla
2020-07-30  0:07       ` Daniel Sangorrin
2020-07-30  5:59         ` Jan Kiszka [this message]
2020-07-23 10:37 ` [cip-dev] [PATCH 1/3] cip-security: Add packages for IEC-62443-4-2 Evaluation Jan Kiszka
2020-07-23 12:53   ` Venkata Pyla
2020-07-23 13:13   ` Venkata Pyla
2020-07-23 13:52     ` Jan Kiszka
2020-07-27  2:47       ` Daniel Sangorrin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=de6bb645-59dc-3ecb-82a6-078684e0a2a1@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=Venkata.Pyla@toshiba-tsip.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=daniel.sangorrin@toshiba.co.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.