* meta-openstack open-iscsi question
@ 2014-07-29 12:44 Alexandru Vaduva
2014-07-29 12:50 ` Bruce Ashfield
0 siblings, 1 reply; 4+ messages in thread
From: Alexandru Vaduva @ 2014-07-29 12:44 UTC (permalink / raw)
To: meta-virtualization@yoctoproject.org
Cc: bruce.ashfield@windriver.com, vu.tran@windriver.com
Hello guys,
I am curious on why do you have in meta-cloud-services duplicated recipes:
open-iscsi-user - iscsi-initiator-utils
open-iscsi-kernel - kernel with open iscsi modules enabled and built.
I can see that the sources available for open-iscsi-kernel are applicable for kernel version < 3,
But I do not understand the uses of both open-iscsi-user and iscsi-initiator-utils because they are building the same information but different version of the sources.
At least so it seems.
Thanks,
Alexandru Vaduva
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: meta-openstack open-iscsi question
2014-07-29 12:44 meta-openstack open-iscsi question Alexandru Vaduva
@ 2014-07-29 12:50 ` Bruce Ashfield
2014-07-29 12:51 ` Alexandru Vaduva
0 siblings, 1 reply; 4+ messages in thread
From: Bruce Ashfield @ 2014-07-29 12:50 UTC (permalink / raw)
To: Alexandru Vaduva, meta-virtualization@yoctoproject.org
Cc: vu.tran@windriver.com
On 14-07-29 08:44 AM, Alexandru Vaduva wrote:
> Hello guys,
>
> I am curious on why do you have in meta-cloud-services duplicated recipes:
> open-iscsi-user - iscsi-initiator-utils
We have modifications to this recipe that I'm working to get into the
original over time.
But I can't hold merging dependent recipes while I wait, so I carry
the changes in meta-cloud-services while that process happens.
> open-iscsi-kernel - kernel with open iscsi modules enabled and built.
>
> I can see that the sources available for open-iscsi-kernel are applicable for kernel version < 3,
The kernel part is only there for completeness sake. We build the
kernel parts from the linux-yocto recipes. Over time, we'll also
be dropping this part .. as Vu knows, I already asked him and am
in the process of removing it.
> But I do not understand the uses of both open-iscsi-user and iscsi-initiator-utils because they are building the same information but different version of the sources.
> At least so it seems.
Again. For completeness sake. We brought in a complete copy of the
HIPOS recipes to work with as part of enabling the backend. That
way I can more easily keep it in sync.
Bruce
>
>
> Thanks,
> Alexandru Vaduva
>
>
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: meta-openstack open-iscsi question
2014-07-29 12:50 ` Bruce Ashfield
@ 2014-07-29 12:51 ` Alexandru Vaduva
2014-07-29 12:58 ` Bruce Ashfield
0 siblings, 1 reply; 4+ messages in thread
From: Alexandru Vaduva @ 2014-07-29 12:51 UTC (permalink / raw)
To: Bruce Ashfield, meta-virtualization@yoctoproject.org
Cc: vu.tran@windriver.com
So you no longer use the open-iscsi-user and open-iscsi-kernel recipes?
-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
Sent: Tuesday, July 29, 2014 3:50 PM
To: Alexandru Vaduva; meta-virtualization@yoctoproject.org
Cc: vu.tran@windriver.com
Subject: Re: meta-openstack open-iscsi question
On 14-07-29 08:44 AM, Alexandru Vaduva wrote:
> Hello guys,
>
> I am curious on why do you have in meta-cloud-services duplicated recipes:
> open-iscsi-user - iscsi-initiator-utils
We have modifications to this recipe that I'm working to get into the original over time.
But I can't hold merging dependent recipes while I wait, so I carry the changes in meta-cloud-services while that process happens.
> open-iscsi-kernel - kernel with open iscsi modules enabled and built.
>
> I can see that the sources available for open-iscsi-kernel are
> applicable for kernel version < 3,
The kernel part is only there for completeness sake. We build the kernel parts from the linux-yocto recipes. Over time, we'll also be dropping this part .. as Vu knows, I already asked him and am in the process of removing it.
> But I do not understand the uses of both open-iscsi-user and iscsi-initiator-utils because they are building the same information but different version of the sources.
> At least so it seems.
Again. For completeness sake. We brought in a complete copy of the HIPOS recipes to work with as part of enabling the backend. That way I can more easily keep it in sync.
Bruce
>
>
> Thanks,
> Alexandru Vaduva
>
>
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: meta-openstack open-iscsi question
2014-07-29 12:51 ` Alexandru Vaduva
@ 2014-07-29 12:58 ` Bruce Ashfield
0 siblings, 0 replies; 4+ messages in thread
From: Bruce Ashfield @ 2014-07-29 12:58 UTC (permalink / raw)
To: Alexandru Vaduva, meta-virtualization@yoctoproject.org
Cc: vu.tran@windriver.com
On 14-07-29 08:51 AM, Alexandru Vaduva wrote:
> So you no longer use the open-iscsi-user and open-iscsi-kernel recipes?
packagegroup-cloud-compute can conditionally use them, I'm not heavily using
that backend, but others are.
Bruce
>
> -----Original Message-----
> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]
> Sent: Tuesday, July 29, 2014 3:50 PM
> To: Alexandru Vaduva; meta-virtualization@yoctoproject.org
> Cc: vu.tran@windriver.com
> Subject: Re: meta-openstack open-iscsi question
>
> On 14-07-29 08:44 AM, Alexandru Vaduva wrote:
>> Hello guys,
>>
>> I am curious on why do you have in meta-cloud-services duplicated recipes:
>> open-iscsi-user - iscsi-initiator-utils
>
> We have modifications to this recipe that I'm working to get into the original over time.
>
> But I can't hold merging dependent recipes while I wait, so I carry the changes in meta-cloud-services while that process happens.
>
>> open-iscsi-kernel - kernel with open iscsi modules enabled and built.
>>
>> I can see that the sources available for open-iscsi-kernel are
>> applicable for kernel version < 3,
>
> The kernel part is only there for completeness sake. We build the kernel parts from the linux-yocto recipes. Over time, we'll also be dropping this part .. as Vu knows, I already asked him and am in the process of removing it.
>
>> But I do not understand the uses of both open-iscsi-user and iscsi-initiator-utils because they are building the same information but different version of the sources.
>> At least so it seems.
>
> Again. For completeness sake. We brought in a complete copy of the HIPOS recipes to work with as part of enabling the backend. That way I can more easily keep it in sync.
>
> Bruce
>
>>
>>
>> Thanks,
>> Alexandru Vaduva
>>
>>
>>
>>
>>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-07-29 12:58 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-07-29 12:44 meta-openstack open-iscsi question Alexandru Vaduva
2014-07-29 12:50 ` Bruce Ashfield
2014-07-29 12:51 ` Alexandru Vaduva
2014-07-29 12:58 ` Bruce Ashfield
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.